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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200212143751.0114fe78@gandalf.local.home>
Date:   Wed, 12 Feb 2020 14:37:51 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Yiwei Zhang <zzyiwei@...gle.com>
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

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