From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: "Souza, Jose" <jose.souza@intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"Nerlige Ramappa, Umesh" <umesh.nerlige.ramappa@intel.com>,
"De Marchi, Lucas" <lucas.demarchi@intel.com>
Subject: Re: [PATCH] drm/xe/uapi: Rename xe perf layer as xe observation layer
Date: Wed, 03 Jul 2024 08:50:57 -0700 [thread overview]
Message-ID: <87r0caa2zi.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <405ecbace1f12fe2d70257da79764fd83d604b7e.camel@intel.com>
On Wed, 03 Jul 2024 08:52:54 -0700, Souza, Jose wrote:
>
> > +static struct ctl_table observation_ctl_table[] = {
> > + {
> > + .procname = "xe_observation_paranoid",
>
> This will lead to /proc/sys/dev/xe/xe_observation_paranoid, is this the intention?
> Before it was /proc/sys/dev/xe/perf_stream_paranoid
Yes, basically the "perf" name is purged and replaced by "observation" (or
"open a perf stream" is now replaced by "open an observation stream").
next prev parent reply other threads:[~2024-07-03 16:09 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 21:40 [PATCH] drm/xe/uapi: Rename xe perf layer as xe observation layer Ashutosh Dixit
2024-07-02 21:48 ` Dixit, Ashutosh
2024-07-03 15:18 ` Rodrigo Vivi
2024-07-02 22:45 ` Umesh Nerlige Ramappa
2024-07-03 0:03 ` Dixit, Ashutosh
2024-07-03 15:03 ` ✓ CI.Patch_applied: success for " Patchwork
2024-07-03 15:03 ` ✗ CI.checkpatch: warning " Patchwork
2024-07-03 15:05 ` ✓ CI.KUnit: success " Patchwork
2024-07-03 15:16 ` ✓ CI.Build: " Patchwork
2024-07-03 15:19 ` ✓ CI.Hooks: " Patchwork
2024-07-03 15:20 ` ✓ CI.checksparse: " Patchwork
2024-07-03 15:48 ` ✓ CI.BAT: " Patchwork
2024-07-03 15:52 ` [PATCH] " Souza, Jose
2024-07-03 15:50 ` Dixit, Ashutosh [this message]
2024-07-03 16:12 ` Souza, Jose
2024-07-03 16:36 ` Dixit, Ashutosh
2024-07-03 16:41 ` Dixit, Ashutosh
2024-07-03 15:53 ` ✓ CI.Patch_applied: success for drm/xe/uapi: Rename xe perf layer as xe observation layer (rev2) Patchwork
2024-07-03 15:54 ` ✗ CI.checkpatch: warning " Patchwork
2024-07-03 15:55 ` ✓ CI.KUnit: success " Patchwork
2024-07-03 16:07 ` ✓ CI.Build: " Patchwork
2024-07-03 16:09 ` ✓ CI.Hooks: " Patchwork
2024-07-03 16:10 ` ✓ CI.checksparse: " Patchwork
2024-07-03 16:37 ` ✗ CI.BAT: failure " Patchwork
2024-07-03 20:58 ` ✓ CI.FULL: success for drm/xe/uapi: Rename xe perf layer as xe observation layer Patchwork
2024-07-03 22:30 ` ✓ CI.FULL: success for drm/xe/uapi: Rename xe perf layer as xe observation layer (rev2) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2024-07-03 16:48 [PATCH] drm/xe/uapi: Rename xe perf layer as xe observation layer Ashutosh Dixit
2024-07-03 17:04 ` Souza, Jose
2024-07-03 18:02 ` Souza, Jose
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=87r0caa2zi.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jose.souza@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=umesh.nerlige.ramappa@intel.com \
/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).