linux-kernel - Re: [PATCH] Add gpu memory tracepoints

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAKT=dDnnSrkGx1KN8t0-c7cqXCCE=xj=usUT9COfmTDbirx5WQ@mail.gmail.com>
Date:   Wed, 12 Feb 2020 11:40:18 -0800
From:   Yiwei Zhang <zzyiwei@...gle.com>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     mingo@...hat.com, linux-kernel@...r.kernel.org,
        Prahlad Kilambi <prahladk@...gle.com>,
        Joel Fernandes <joelaf@...gle.com>,
        android-kernel <android-kernel@...gle.com>
Subject: Re: [PATCH] Add gpu memory tracepoints

Thanks for the info! I'll update the patch accordingly.

Best regards,
Yiwei

On Wed, Feb 12, 2020 at 11:37 AM Steven Rostedt <rostedt@...dmis.org> wrote:
>
> On Wed, 12 Feb 2020 11:26:08 -0800
> Yiwei Zhang <zzyiwei@...gle.com> wrote:
>
> > Hi Steven,
> >
> > I can move the stuff out from the kernel/trace. Then can we still
> > leave include/trace/events/gpu_mem.h where it is right now? Or do we
> > have to move that out as well? Because we would need a non-drm common
> > header place for the tracepoint so that downstream drivers can find
> > the tracepoint definition.
> >
>
> You can leave the header there. The include/trace/events/ is the place
> to put trace event headers for common code.
>
> It just did not belong in kernel/trace/
>
> Thanks!
>
> -- Steve