From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-xe@lists.freedesktop.org,
Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>,
Jose Souza <jose.souza@intel.com>,
Jonathan Cavitt <jonathan.cavitt@intel.com>
Subject: Re: [PATCH] drm/xe/oa: Enable Xe2+ PES disaggregation
Date: Tue, 10 Sep 2024 22:03:56 -0700 [thread overview]
Message-ID: <87ttemzsqr.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <slkwdfygztw67triuhz4bihzqke2yrmgyfptbw43tanx5x5c3d@rcz36pcnshap>
On Tue, 10 Sep 2024 17:57:59 -0700, Lucas De Marchi wrote:
>
> On Tue, Sep 10, 2024 at 05:40:02PM GMT, Ashutosh Dixit wrote:
> > On Tue, 10 Sep 2024 10:04:32 -0700, Lucas De Marchi wrote:
> >>
> >
> > Hi Lucas,
> >
> > We had a whole email thread to figure this out :/
> >
> >> On Mon, Sep 09, 2024 at 09:59:33AM GMT, Ashutosh Dixit wrote:
> >> > Xe2+ PES disaggregation for OAG needs to be enabled to obtain disaggregated
> >> > metrics when disaggregated data is needed. There is no uapi impact of this
> >>
> >> it looks like the *control* for disaggregated data is only available on
> >> xe2
> >
> > Correct, that is why the check below (also this is available only for OAG,
> > not say for OAM):
> >
> > if (GRAPHICS_VER(stream->oa->xe) >= 20 &&
> > stream->hwe->oa_unit->type == DRM_XE_OA_UNIT_TYPE_OAG)
> >
> >> and we always use disaggregated, right?
> >
> > No we don't, please see below.
> >
> >>
> >> > change.
> >> >
> >> > v2: Minor change to commit message
> >> >
> >> > Bspec: 61101
> >>
> >> "Note: After enabling desired disaggregation mode/s using this control
> >> field, PES MODE_SELECT field is used to configure appropriate
> >> disaggregation mode of corresponding PEC."
> >>
> >> Apparently MODE_SELECT == Aggregated is the hw default for xe2. Don't
> >> we need to program anything else?
> >
> > So the code in this patch only enables disaggregation, this additional step
> > (PES_MODE_SELECT) is still needed to actually use disaggregation. However
> > this second step is done via OA configurations which come in from userspace
> > (using add_config observation stream op). So userspace can request either
> > aggregated or disaggregated data depending on the OA config it programs.
> >
> > The goal of this patch is only to enable disaggregation so userspace can
> > use it if they want, otherwise they can't, they can only use
> > aggregated.
>
> can you add a paragraph to the commit message stating something like
> above? Because it was not clear it was intentional to enable it in the
> control and not in the PES_MODE_SELECT.
I have changed the commit message to the following:
"
Enable Xe2+ PES disaggregation (for OAG) to retrieve disaggregated metrics
when disaggregated data is needed. Userspace can select whether to receive
aggregated or disaggregated metrics via the particular OA configuration it
uses (programmed via DRM_XE_OBSERVATION_OP_ADD_CONFIG).
"
I think this provides sufficient high level information, not bringing in
stuff like PES_MODE_SELECT. Or should I mention PES_MODE_SELECT too?
Thanks.
>
> thanks
> Lucas De Marchi
next prev parent reply other threads:[~2024-09-11 5:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 16:59 [PATCH] drm/xe/oa: Enable Xe2+ PES disaggregation Ashutosh Dixit
2024-09-09 17:04 ` ✓ CI.Patch_applied: success for drm/xe/oa: Enable Xe2+ PES disaggregation (rev2) Patchwork
2024-09-09 17:05 ` ✓ CI.checkpatch: " Patchwork
2024-09-09 17:06 ` ✓ CI.KUnit: " Patchwork
2024-09-09 17:18 ` ✓ CI.Build: " Patchwork
2024-09-09 17:20 ` ✓ CI.Hooks: " Patchwork
2024-09-09 17:21 ` ✓ CI.checksparse: " Patchwork
2024-09-09 18:05 ` ✓ CI.BAT: " Patchwork
2024-09-09 22:30 ` ✗ CI.FULL: failure " Patchwork
2024-09-10 17:04 ` [PATCH] drm/xe/oa: Enable Xe2+ PES disaggregation Lucas De Marchi
2024-09-11 0:40 ` Dixit, Ashutosh
2024-09-11 0:57 ` Lucas De Marchi
2024-09-11 5:03 ` Dixit, Ashutosh [this message]
2024-09-11 15:58 ` Lucas De Marchi
2024-09-11 18:48 ` Dixit, Ashutosh
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=87ttemzsqr.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jonathan.cavitt@intel.com \
--cc=jose.souza@intel.com \
--cc=lucas.demarchi@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