Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Riana Tauro <riana.tauro@intel.com>
Cc: intel-xe@lists.freedesktop.org, anshuman.gupta@intel.com,
	aravind.iddamsetty@linux.intel.com, rodrigo.vivi@intel.com,
	umesh.nerlige.ramappa@intel.com, krishnaiah.bommu@intel.com
Subject: Re: [PATCH v9 0/2] drm/xe/pmu: Enable PMU interface
Date: Fri, 14 Jun 2024 08:34:30 -0700	[thread overview]
Message-ID: <875xubtu61.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <af6df0d8-bafa-4fd5-a747-ff9e3092c3c6@intel.com>

On Thu, 13 Jun 2024 22:50:39 -0700, Riana Tauro wrote:
>
> Hi Ashutosh
>
> On 6/14/2024 12:09 AM, Dixit, Ashutosh wrote:
> > On Thu, 13 Jun 2024 03:04:09 -0700, Riana Tauro wrote:
> >>
> >
> > Hi Riana,
> >
> >> There are a set of engine group busyness counters provided by HW which are
> >> perfect fit to be exposed via PMU perf events.
> >>
> >> BSPEC: 46559, 46560, 46722, 46729, 52071, 71028
> >>
> >> events can be listed using:
> >> perf list
> >>    xe_0000_03_00.0/any-engine-group-busy-gt0/         [Kernel PMU event]
> >>    xe_0000_03_00.0/copy-group-busy-gt0/               [Kernel PMU event]
> >>    xe_0000_03_00.0/media-group-busy-gt0/              [Kernel PMU event]
> >>    xe_0000_03_00.0/render-group-busy-gt0/             [Kernel PMU event]
> >
> > PMU patches merged previously were dropped in 90a8b23f9b85 ("drm/xe/pmu:
> > Remove PMU from Xe till uapi is finalized") because PMU uapi was expected
> > to change. Why are we re-posting these old patches again now, without
> > including the planned uapi changes?
>
> The uapi changes were dropped and there are no other upcoming changes for
> Group busyness. So re-posted the old series.

What happened to VF busyness (which is why I thought the uapi was going to
change)?

>
> Thanks,
> Riana
> >
> > Thanks.
> > --
> > Ashutosh

  reply	other threads:[~2024-06-14 15:53 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13 10:04 [PATCH v9 0/2] drm/xe/pmu: Enable PMU interface Riana Tauro
2024-06-13  9:57 ` ✓ CI.Patch_applied: success for drm/xe/pmu: Enable PMU interface (rev9) Patchwork
2024-06-13  9:57 ` ✗ CI.checkpatch: warning " Patchwork
2024-06-13  9:59 ` ✓ CI.KUnit: success " Patchwork
2024-06-13 10:04 ` [PATCH v9 1/2] drm/xe: Get GT clock to nanosecs Riana Tauro
2024-06-14 14:57   ` Lucas De Marchi
2024-06-13 10:04 ` [PATCH v9 2/2] drm/xe/pmu: Enable PMU interface Riana Tauro
2024-06-14 16:15   ` Lucas De Marchi
2024-06-14 16:38     ` Tvrtko Ursulin
2024-06-14 20:54   ` Ghimiray, Himal Prasad
2024-06-27  5:21     ` Riana Tauro
2024-06-20 19:52   ` Umesh Nerlige Ramappa
2024-06-27  6:49     ` Aravind Iddamsetty
2024-06-27 16:05       ` Umesh Nerlige Ramappa
2024-06-28  9:41         ` Aravind Iddamsetty
2024-06-28 16:36           ` Umesh Nerlige Ramappa
2024-06-28 15:55     ` Lucas De Marchi
2024-06-28 16:52       ` Umesh Nerlige Ramappa
2024-06-28 18:24         ` Lucas De Marchi
2024-06-28 18:49           ` Umesh Nerlige Ramappa
2024-06-13 10:11 ` ✓ CI.Build: success for drm/xe/pmu: Enable PMU interface (rev9) Patchwork
2024-06-13 10:13 ` ✗ CI.Hooks: failure " Patchwork
2024-06-13 10:14 ` ✓ CI.checksparse: success " Patchwork
2024-06-13 11:48 ` ✓ CI.BAT: " Patchwork
2024-06-13 18:39 ` [PATCH v9 0/2] drm/xe/pmu: Enable PMU interface Dixit, Ashutosh
2024-06-14  5:50   ` Riana Tauro
2024-06-14 15:34     ` Dixit, Ashutosh [this message]
2024-06-20 19:15       ` Umesh Nerlige Ramappa
2024-06-21  4:29         ` Aravind Iddamsetty
2024-06-21 18:32           ` Umesh Nerlige Ramappa
2024-06-24 10:27             ` Aravind Iddamsetty
2024-06-24 23:23               ` Umesh Nerlige Ramappa

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=875xubtu61.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=aravind.iddamsetty@linux.intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=krishnaiah.bommu@intel.com \
    --cc=riana.tauro@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