From: Chris Wilson <chris@chris-wilson.co.uk>
To: Lionel Landwerlin <lionel.g.landwerlin@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 2/2] RFC drm/i915: Export per-client debug tracing
Date: Sun, 01 Mar 2020 16:33:06 +0000 [thread overview]
Message-ID: <158308038685.3365.12116750291008658412@skylake-alporthouse-com> (raw)
In-Reply-To: <74b581c4-2e5b-6455-63d3-351635820a4b@intel.com>
Quoting Lionel Landwerlin (2020-03-01 16:27:24)
> On 01/03/2020 17:52, Chris Wilson wrote:
> > Rather than put sensitive, and often voluminous, user details into a
> > global dmesg, report the error and debug messages directly back to the
> > user via the kernel tracing mechanism.
>
>
> Sounds really nice. Don't you want the existing global tracing to be the
> default at least until a client does a get_trace?
We've currently in the middle of an awfully spammy regression :(
And I think the user's debug information does not belong in the global
dmesg.
-Chris
next prev parent reply other threads:[~2020-03-01 16:33 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 [this message]
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
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=158308038685.3365.12116750291008658412@skylake-alporthouse-com \
--to=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lionel.g.landwerlin@intel.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).