All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Daniel Vetter <daniel@ffwll.ch>,
	Gurchetan Singh <gurchetansingh@chromium.org>,
	dri-devel@lists.freedesktop.org, kaleshsingh@google.com
Subject: Re: [RFC PATCH 1/8] tracing/gpu: modify gpu_mem_total
Date: Thu, 28 Oct 2021 17:21:37 +0200	[thread overview]
Message-ID: <YXrAAZlxxStNFG/K@phenom.ffwll.local> (raw)
In-Reply-To: <20211021090715.2318259d@gandalf.local.home>

On Thu, Oct 21, 2021 at 09:07:15AM -0400, Steven Rostedt wrote:
> On Thu, 21 Oct 2021 13:56:38 +0200
> Daniel Vetter <daniel@ffwll.ch> wrote:
> 
> > Yay, that patch is just impressive. Lands a new gpu tracepoints, never
> > even showed up on the gpu subsystem discussion list.
> 
> I'm guessing there was some confusion. When this was first introduced, I
> stated it needs to go into the gpu tree, which a new set of patches included
> more Cc's. I never checked if those Cc's were for the GPU maintainers or not
> (I assumed they were).
> 
>  https://lore.kernel.org/all/20200224113805.134f8b95@gandalf.local.home/
> 
> I'm not sure where Yiwei Zhang got his email list for the GPU maintainers
> from. As he obviously thought it was going to them.
> 
>  https://lore.kernel.org/all/CAKT=dDnFpj2hJd5z73pfcrhXXacDpPVyKzC7+K94tsX=+e_BHg@mail.gmail.com/
> 
> Seeing that this patch set is going through dri-devel list, which I'm
> guessing is also for GPU, even though it's not under that in the
> MAINTAINERS file:
> 
> DRM DRIVERS AND MISC GPU PATCHES
> M:      Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> M:      Maxime Ripard <mripard@kernel.org>
> M:      Thomas Zimmermann <tzimmermann@suse.de>
> S:      Maintained
> W:      https://01.org/linuxgraphics/gfx-docs/maintainer-tools/drm-misc.html
> T:      git git://anongit.freedesktop.org/drm/drm-misc
> F:      Documentation/gpu/
> F:      drivers/gpu/drm/*
> F:      drivers/gpu/vga/
> F:      include/drm/drm*
> F:      include/linux/vga*
> F:      include/uapi/drm/drm*
> 
> Should the list be added there?
> 
> I've been struggling with this patch set because nobody claimed ownership
> for it. But now I believe we have one (you? :-)  And I can now just comment
> on the tracing POV and leave the content and usability to you folks ;-)

Hm we indeed don't have an entry for drivers/gpu, but there is one for
gpu/drm overall:

DRM DRIVERS
M:	David Airlie <airlied@linux.ie>
M:	Daniel Vetter <daniel@ffwll.ch>
L:	dri-devel@lists.freedesktop.org
S:	Maintained
B:	https://gitlab.freedesktop.org/drm
C:	irc://irc.oftc.net/dri-devel
T:	git git://anongit.freedesktop.org/drm/drm
F:	Documentation/devicetree/bindings/display/
F:	Documentation/devicetree/bindings/gpu/
F:	Documentation/gpu/
F:	drivers/gpu/drm/
F:	drivers/gpu/vga/
F:	include/drm/
F:	include/linux/vga*
F:	include/uapi/drm/

I'll do a patch to include drivers/gpu here, not sure why that's
different.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

  reply	other threads:[~2021-10-28 15:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-21  3:10 [RFC PATCH 0/8] GPU memory tracepoints Gurchetan Singh
2021-10-21  3:10 ` [RFC PATCH 1/8] tracing/gpu: modify gpu_mem_total Gurchetan Singh
2021-10-21 11:56   ` Daniel Vetter
2021-10-21 13:07     ` Steven Rostedt
2021-10-28 15:21       ` Daniel Vetter [this message]
2021-10-21  3:10 ` [RFC PATCH 2/8] drm: add new tracepoint fields to drm_device and drm_file Gurchetan Singh
2021-10-21  3:10 ` [RFC PATCH 3/8] drm: add helper functions for gpu_mem_total and gpu_mem_instance Gurchetan Singh
2021-10-21  3:10 ` [RFC PATCH 4/8] drm: start using drm_gem_trace_gpu_mem_total Gurchetan Singh
2021-10-21  3:49   ` Steven Rostedt
2021-10-21  3:10 ` [RFC PATCH 5/8] drm: start using drm_gem_trace_gpu_mem_instance Gurchetan Singh
2021-10-21  3:50   ` Steven Rostedt
2021-11-05  8:24   ` [drm] a31246115b: BUG:kernel_NULL_pointer_dereference,address kernel test robot
2021-11-05  8:24     ` kernel test robot
2021-10-21  3:10 ` [RFC PATCH 6/8] drm: track real and fake imports in drm_prime_member Gurchetan Singh
2021-10-21  3:10 ` [RFC PATCH 7/8] drm: trace memory import per DRM file Gurchetan Singh
2021-10-21  3:10 ` [RFC PATCH 8/8] drm: trace memory import per DRM device Gurchetan Singh
2021-10-21 12:00 ` [RFC PATCH 0/8] GPU memory tracepoints Daniel Vetter
2021-10-21 22:38   ` Kalesh Singh
2021-11-01 18:54     ` Kalesh Singh
2021-11-17 18:06       ` Kalesh Singh

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=YXrAAZlxxStNFG/K@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gurchetansingh@chromium.org \
    --cc=kaleshsingh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.