From: Steven Rostedt <rostedt@goodmis.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] trace: Export anonymous tracing
Date: Sun, 1 Mar 2020 19:36:49 -0500 [thread overview]
Message-ID: <20200301193649.71da6747@oasis.local.home> (raw)
In-Reply-To: <158310134594.5508.5362429296192213548@skylake-alporthouse-com>
On Sun, 01 Mar 2020 22:22:25 +0000
Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > I'm curious to why we need it to be anonymous. Why not allow them to be
> > visible from the tracing directory. This could allow for easier
> > debugging. Note, the trace instances have ref counters thus they can't
> > be removed if something has a reference to it.
>
> Do you really want a few thousand (or even tens) i915-client-%d? That
> does not particularly seem like it adds ease-of-use, and would need to be
> restricted to the client [or root]. The intent is for the client to have
> a private channel for detailed debug/error reporting of its own calls
> into the kernel.
Wow! I didn't expect this to have that many anonymous users. What is
the use case for again?
-- Steve
next prev parent reply other threads:[~2020-03-02 0:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-01 15:52 [PATCH 1/2] trace: Export anonymous tracing Chris Wilson
2020-03-01 15:52 ` [PATCH 2/2] RFC drm/i915: Export per-client debug tracing Chris Wilson
2020-03-01 16:27 ` [Intel-gfx] " Lionel Landwerlin
2020-03-01 16:33 ` Chris Wilson
2020-03-02 12:06 ` Daniel Vetter
2020-03-01 18:18 ` [PATCH 1/2] trace: Export anonymous tracing Steven Rostedt
2020-03-01 22:22 ` Chris Wilson
2020-03-02 0:36 ` Steven Rostedt [this message]
2020-03-03 23:24 ` Steven Rostedt
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=20200301193649.71da6747@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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