From: "Iddamsetty, Aravind" <aravind.iddamsetty@intel.com>
To: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
Cc: Bommu Krishnaiah <krishnaiah.bommu@intel.com>,
intel-xe@lists.freedesktop.org,
Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Subject: Re: [Intel-xe] [PATCH v3 2/2] drm/xe/pmu: Enable PMU interface
Date: Wed, 9 Aug 2023 18:41:48 +0530 [thread overview]
Message-ID: <cec5ddd7-e79f-c848-653f-81e21240f29a@intel.com> (raw)
In-Reply-To: <b9496a4b-bea2-fa15-6ae1-5810baf70260@intel.com>
On 09-08-2023 17:27, Iddamsetty, Aravind wrote:
>
>
> On 09-08-2023 15:25, Iddamsetty, Aravind wrote:
>>
>>
>> On 09-08-2023 12:58, Dixit, Ashutosh wrote:
>>
>> Hi Ashutosh,
>>
>>> On Tue, 08 Aug 2023 04:54:36 -0700, Aravind Iddamsetty wrote:
>>>>
>>>
>>> Hi Aravind,
>>>
>>> Spotted a few remaining things. See if it's possible to fix these up and
>>> send another version.
>>>
>>>> diff --git a/drivers/gpu/drm/xe/xe_pmu.c b/drivers/gpu/drm/xe/xe_pmu.c
>>>> new file mode 100644
>>>> index 000000000000..9637f8283641
>>>> --- /dev/null
>>>> +++ b/drivers/gpu/drm/xe/xe_pmu.c
>>>> @@ -0,0 +1,673 @@
>>
>> <snip>
>>>> +static u64 __engine_group_busyness_read(struct xe_gt *gt, int sample_type)
>>>> +{
>>>> + u64 val = 0;
>>>> +
>>>
>>> What is the forcewake domain for these registers? Don't we need to get
>>> forcewake before reading these. Something like:
>>>
>>> XE_WARN_ON(xe_force_wake_get(gt_to_fw(gt), XE_FORCEWAKE_ALL));
>>
>> based on BSPEC:67609 these belong to GT power domain, so acquiring that
>> should be sufficient.
>
> But if i understand correctly taking forcewake is not allowed here as it
> is an atomic context and forcewake can sleep and that is what I'm seeing
> as well, might also be the reason why i915 didn't do that as well.
>
> [ 899.114316] BUG: sleeping function called from invalid context at
> kernel/locking/mutex.c:580
> [ 899.115768] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid:
> 290, name: kworker/27:1
that is the reason why in i915 we were doing similar thing of storing
the counter as we enter rc6, not sure how do we do that in xe.
Thanks,
Aravind.
>
>
> Thanks,
> Aravind.
>>>
>>>> + switch (sample_type) {
>>>> + case __XE_SAMPLE_RENDER_GROUP_BUSY:
>>>> + val = xe_mmio_read32(gt, XE_OAG_RENDER_BUSY_FREE);
>>>> + break;
>>>> + case __XE_SAMPLE_COPY_GROUP_BUSY:
>>>> + val = xe_mmio_read32(gt, XE_OAG_BLT_BUSY_FREE);
>>>> + break;
>>>> + case __XE_SAMPLE_MEDIA_GROUP_BUSY:
>>>> + val = xe_mmio_read32(gt, XE_OAG_ANY_MEDIA_FF_BUSY_FREE);
>>>> + break;
>>>> + case __XE_SAMPLE_ANY_ENGINE_GROUP_BUSY:
>>>> + val = xe_mmio_read32(gt, XE_OAG_RC0_ANY_ENGINE_BUSY_FREE);
>>>> + break;
>>>> + default:
>>>> + drm_warn(>->tile->xe->drm, "unknown pmu event\n");
>>>> + }
>>>
>>> And similarly here:
>>>
>>> XE_WARN_ON(xe_force_wake_put(gt_to_fw(gt), XE_FORCEWAKE_ALL));
>>>
>>
>> Thanks,
>> Aravind.
>>
>> <snip>
>>>
>>> Thanks.
>>> --
>>> Ashutosh
next prev parent reply other threads:[~2023-08-09 13:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 11:54 [Intel-xe] [PATCH v3 0/2] drm/xe/pmu: Enable PMU interface Aravind Iddamsetty
2023-08-08 11:54 ` [Intel-xe] [PATCH v3 1/2] drm/xe: Get GT clock to nanosecs Aravind Iddamsetty
2023-08-09 5:08 ` Dixit, Ashutosh
2023-08-09 11:07 ` Iddamsetty, Aravind
2023-08-08 11:54 ` [Intel-xe] [PATCH v3 2/2] drm/xe/pmu: Enable PMU interface Aravind Iddamsetty
2023-08-09 7:28 ` Dixit, Ashutosh
2023-08-09 7:46 ` Iddamsetty, Aravind
2023-08-09 11:39 ` Iddamsetty, Aravind
2023-08-10 2:17 ` Dixit, Ashutosh
2023-08-10 2:06 ` Dixit, Ashutosh
2023-08-09 9:55 ` Iddamsetty, Aravind
2023-08-09 11:57 ` Iddamsetty, Aravind
2023-08-09 13:11 ` Iddamsetty, Aravind [this message]
2023-08-10 2:40 ` Dixit, Ashutosh
2023-08-10 8:10 ` Iddamsetty, Aravind
2023-08-10 21:55 ` Rodrigo Vivi
2023-08-11 3:38 ` Dixit, Ashutosh
2023-08-11 6:17 ` Iddamsetty, Aravind
2023-08-11 19:17 ` Dixit, Ashutosh
2023-08-14 2:02 ` Dixit, Ashutosh
2023-08-14 4:19 ` Iddamsetty, Aravind
2023-08-08 12:08 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe/pmu: Enable PMU interface (rev3) Patchwork
2023-08-08 12:09 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-08-08 12:10 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-08-08 12:14 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-08-08 12:14 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-08-08 12:14 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-08-08 12:51 ` [Intel-xe] ✗ CI.BAT: failure " 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=cec5ddd7-e79f-c848-653f-81e21240f29a@intel.com \
--to=aravind.iddamsetty@intel.com \
--cc=ashutosh.dixit@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=krishnaiah.bommu@intel.com \
--cc=tvrtko.ursulin@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