linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yiwei Zhang <zzyiwei@google.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org,
	Prahlad Kilambi <prahladk@google.com>,
	Joel Fernandes <joelaf@google.com>,
	android-kernel <android-kernel@google.com>
Subject: Re: [PATCH] Add gpu memory tracepoints
Date: Wed, 12 Feb 2020 11:40:18 -0800	[thread overview]
Message-ID: <CAKT=dDnnSrkGx1KN8t0-c7cqXCCE=xj=usUT9COfmTDbirx5WQ@mail.gmail.com> (raw)
In-Reply-To: <20200212143751.0114fe78@gandalf.local.home>

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@goodmis.org> wrote:
>
> On Wed, 12 Feb 2020 11:26:08 -0800
> Yiwei Zhang <zzyiwei@google.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

      reply	other threads:[~2020-02-12 19:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11  1:16 [PATCH] Add gpu memory tracepoints zzyiwei
2020-02-11  1:17 ` Yiwei Zhang
2020-02-11  1:22   ` Yiwei Zhang
2020-02-11  2:19 ` Steven Rostedt
2020-02-11  3:05   ` Yiwei Zhang
2020-02-11  3:15     ` Steven Rostedt
2020-02-12 19:26       ` Yiwei Zhang
2020-02-12 19:37         ` Steven Rostedt
2020-02-12 19:40           ` Yiwei Zhang [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKT=dDnnSrkGx1KN8t0-c7cqXCCE=xj=usUT9COfmTDbirx5WQ@mail.gmail.com' \
    --to=zzyiwei@google.com \
    --cc=android-kernel@google.com \
    --cc=joelaf@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=prahladk@google.com \
    --cc=rostedt@goodmis.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).