From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2 8/9] drm/i915/perf: Add engine class instance parameters to perf
Date: Tue, 21 Feb 2023 16:10:17 -0800 [thread overview]
Message-ID: <878rgqblw6.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <87a616bmne.wl-ashutosh.dixit@intel.com>
On Tue, 21 Feb 2023 15:53:57 -0800, Dixit, Ashutosh wrote:
>
> > + /**
> > + * In platforms with multiple OA buffers, the engine class instance must
> > + * be passed to open a stream to a OA unit corresponding to the engine.
> > + * Multiple engines may be mapped to the same OA unit.
> > + *
> > + * In addition to the class:instance, if a gem context is also passed, then
> > + * 1) the report headers of OA reports from other engines are squashed.
>
> Other engines or you mean other contexts?
>
> > + * 2) OAR is enabled for the class:instance
>
> For render engine?
I think this means the engine will support MI_REPORT_PERF_COUNT but not
sure how this (or if anything) is done.
next prev parent reply other threads:[~2023-02-22 0:11 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 0:58 [Intel-gfx] [PATCH v2 0/9] Add OAM support for MTL Umesh Nerlige Ramappa
2023-02-17 0:58 ` [Intel-gfx] [PATCH v2 1/9] drm/i915/perf: Drop wakeref on GuC RC error Umesh Nerlige Ramappa
2023-02-17 0:58 ` [Intel-gfx] [PATCH v2 2/9] drm/i915/perf: Add helper to check supported OA engines Umesh Nerlige Ramappa
2023-02-17 0:58 ` [Intel-gfx] [PATCH v2 3/9] drm/i915/perf: Validate OA sseu config outside switch Umesh Nerlige Ramappa
2023-02-17 1:10 ` Dixit, Ashutosh
2023-02-17 0:58 ` [Intel-gfx] [PATCH v2 4/9] drm/i915/perf: Group engines into respective OA groups Umesh Nerlige Ramappa
2023-02-22 21:52 ` Dixit, Ashutosh
2023-02-24 17:30 ` Umesh Nerlige Ramappa
2023-02-17 0:58 ` [Intel-gfx] [PATCH v2 5/9] drm/i915/perf: Fail modprobe if i915_perf_init fails on OOM Umesh Nerlige Ramappa
2023-02-17 2:04 ` Dixit, Ashutosh
2023-02-17 9:55 ` Jani Nikula
2023-02-17 0:58 ` [Intel-gfx] [PATCH v2 6/9] drm/i915/perf: Parse 64bit report header formats correctly Umesh Nerlige Ramappa
2023-02-21 22:14 ` Dixit, Ashutosh
2023-02-17 0:58 ` [Intel-gfx] [PATCH v2 7/9] drm/i915/perf: Handle non-power-of-2 reports Umesh Nerlige Ramappa
2023-02-17 20:58 ` Dixit, Ashutosh
2023-02-18 0:05 ` Umesh Nerlige Ramappa
2023-02-18 1:57 ` Dixit, Ashutosh
2023-02-21 18:51 ` Dixit, Ashutosh
2023-02-24 19:12 ` Umesh Nerlige Ramappa
2023-02-17 0:58 ` [Intel-gfx] [PATCH v2 8/9] drm/i915/perf: Add engine class instance parameters to perf Umesh Nerlige Ramappa
2023-02-17 23:37 ` Umesh Nerlige Ramappa
2023-02-21 23:53 ` Dixit, Ashutosh
2023-02-22 0:10 ` Dixit, Ashutosh [this message]
2023-02-24 19:37 ` Umesh Nerlige Ramappa
2023-02-24 20:48 ` Dixit, Ashutosh
2023-02-17 0:58 ` [Intel-gfx] [PATCH v2 9/9] drm/i915/perf: Add support for OA media units Umesh Nerlige Ramappa
2023-02-17 23:37 ` Umesh Nerlige Ramappa
2023-02-23 20:05 ` Dixit, Ashutosh
2023-02-25 0:58 ` Umesh Nerlige Ramappa
2023-02-25 3:58 ` Dixit, Ashutosh
2023-02-17 1:35 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Add OAM support for MTL (rev2) Patchwork
2023-02-17 1:55 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-02-17 16:09 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=878rgqblw6.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--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