From: Riana Tauro <riana.tauro@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <anshuman.gupta@intel.com>,
<umesh.nerlige.ramappa@intel.com>, <rodrigo.vivi@intel.com>,
<vinay.belgaumkar@intel.com>, <aravind.iddamsetty@intel.com>,
<john.c.harrison@intel.com>, <ashutosh.dixit@intel.com>,
<soham.purkait@intel.com>
Subject: Re: [PATCH v2 7/8] drm/xe/guc: Expose engine busyness only for supported GuC version
Date: Fri, 13 Dec 2024 11:40:38 +0530 [thread overview]
Message-ID: <588b5829-e5fc-4450-bf83-4f2cf05cf29b@intel.com> (raw)
In-Reply-To: <htcdqjyj75ymzb6ywe6wczq7vyhop4cocco7pj26sseajtlmo5@hafxw5sqtbj7>
On 12/13/2024 11:34 AM, Lucas De Marchi wrote:
> On Fri, Dec 13, 2024 at 11:30:38AM +0530, Riana Tauro wrote:
>> Hi Lucas
>>
>> On 12/13/2024 11:14 AM, Lucas De Marchi wrote:
>>> On Thu, Nov 21, 2024 at 12:09:03PM +0530, Riana Tauro wrote:
>>>> Engine busyness is supported only on GuC versions >= 70.32.0
>>>> Allow enabling/reading engine busyness only on supported
>>>> GuC versions. Warn once if not supported.
>>>
>>> did i915 used a different version of the guc api?
>>>
>>> There's no platform supporting GuC >= 70.32.0. We will need to add one
>>> to be able to test.
>> Requested for this guc version. Will merge this once CI passes with
>> the required version.
>
> this means you also need the igt ready for that. Is it done?
Yeah igt is ready and has been tested locally.
Waiting for other tests of pmu to be pushed
https://patchwork.freedesktop.org/series/140737/, to avoid re-sending
these patches again. Will send it once these are pushed> Lucas De Marchi
>
>>
>> Thanks
>> Riana
>>>
>>> Lucas De Marchi
>>
next prev parent reply other threads:[~2024-12-13 6:10 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 6:38 [PATCH v2 0/8] Add PMU support for single engine busyness Riana Tauro
2024-11-21 6:33 ` ✓ CI.Patch_applied: success for Add PMU support for single engine busyness (rev2) Patchwork
2024-11-21 6:34 ` ✗ CI.checkpatch: warning " Patchwork
2024-11-21 6:35 ` ✓ CI.KUnit: success " Patchwork
2024-11-21 6:38 ` [PATCH v2 1/8] [DO NOT REVIEW] drm/xe/pmu: Enable PMU interface Riana Tauro
2024-11-21 6:38 ` [PATCH v2 2/8] [DO NOT REVIEW] drm/xe/pmu: Add GT C6 events Riana Tauro
2024-11-21 6:38 ` [PATCH v2 3/8] [DO NOT REVIEW] drm/xe/pmu: Add GT frequency events Riana Tauro
2024-11-21 6:39 ` [PATCH v2 4/8] drm/xe: add function to convert xe hw engine class to user class Riana Tauro
2024-12-10 23:48 ` Umesh Nerlige Ramappa
2024-12-18 7:33 ` Riana Tauro
2024-12-19 0:13 ` Umesh Nerlige Ramappa
2024-11-21 6:39 ` [PATCH v2 5/8] drm/xe: Add single engine busyness support Riana Tauro
2024-12-12 23:56 ` Umesh Nerlige Ramappa
2024-12-13 0:52 ` Lucas De Marchi
2024-12-13 7:06 ` Riana Tauro
2024-12-13 14:15 ` Lucas De Marchi
2024-12-13 6:22 ` Riana Tauro
2024-11-21 6:39 ` [PATCH v2 6/8] drm/xe/trace: Add trace for xe_engine_activity Riana Tauro
2024-11-21 6:39 ` [PATCH v2 7/8] drm/xe/guc: Expose engine busyness only for supported GuC version Riana Tauro
2024-12-13 5:44 ` Lucas De Marchi
2024-12-13 6:00 ` Riana Tauro
2024-12-13 6:04 ` Lucas De Marchi
2024-12-13 6:10 ` Riana Tauro [this message]
2024-12-13 17:26 ` Lucas De Marchi
2024-12-19 0:19 ` John Harrison
2024-11-21 6:39 ` [PATCH v2 8/8] drm/xe/pmu: Add PMU support for engine busyness Riana Tauro
2024-12-13 5:58 ` Lucas De Marchi
2024-12-18 5:12 ` Riana Tauro
2024-12-18 14:13 ` Lucas De Marchi
2024-12-18 14:51 ` Riana Tauro
2024-12-19 5:47 ` Riana Tauro
2024-12-19 18:46 ` Umesh Nerlige Ramappa
2025-01-06 14:06 ` Riana Tauro
2024-11-21 6:53 ` ✓ CI.Build: success for Add PMU support for single engine busyness (rev2) Patchwork
2024-11-21 6:55 ` ✗ CI.Hooks: failure " Patchwork
2024-11-21 6:57 ` ✓ CI.checksparse: success " Patchwork
2024-11-21 7:17 ` ✗ Xe.CI.BAT: failure " Patchwork
2024-11-21 13:52 ` ✗ Xe.CI.Full: " 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=588b5829-e5fc-4450-bf83-4f2cf05cf29b@intel.com \
--to=riana.tauro@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=aravind.iddamsetty@intel.com \
--cc=ashutosh.dixit@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=john.c.harrison@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=soham.purkait@intel.com \
--cc=umesh.nerlige.ramappa@intel.com \
--cc=vinay.belgaumkar@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