From: Riana Tauro <riana.tauro@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>,
Lucas De Marchi <lucas.demarchi@intel.com>,
Karthik Poosa <karthik.poosa@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <anshuman.gupta@intel.com>,
<umesh.nerlige.ramappa@intel.com>, <sk.anirban@intel.com>,
<soham.purkait@intel.com>
Subject: Re: [PATCH] drm/xe/xe_pmu: Validate gt in event supported
Date: Wed, 2 Jul 2025 10:24:28 +0530 [thread overview]
Message-ID: <d524d82e-00dd-4881-82a1-1ffcea682138@intel.com> (raw)
In-Reply-To: <20250701211954.GM4868@mdroper-desk1.amr.corp.intel.com>
Hi Matt/Lucas
On 7/2/2025 2:49 AM, Matt Roper wrote:
> On Tue, Jul 01, 2025 at 04:09:44PM -0500, Lucas De Marchi wrote:
>> On Tue, Jul 01, 2025 at 01:31:28PM -0700, Matt Roper wrote:
>>> On Mon, Jun 30, 2025 at 05:28:53PM -0500, Lucas De Marchi wrote:
>>>> On Mon, Jun 30, 2025 at 03:07:41PM +0530, Riana Tauro wrote:
>>>>> Validate gt instead of checking gt_id is lesser
>>>>> than max gts per tile
>>>>
>>>> I prefer the series from Matt Roper that is refactoring this part well.
>>>
>>> I think we want this change regardless. My series is about refactoring
>>> to future-proof the behavior in case we wind up with multi-tile+multi-GT
>>> platforms in the future. However Riana's patch here is fixing a real
>>> bug in the code that exists for existing platforms like PVC (i.e., the
>>> code currently lets "GT1" through as valid even on single-tile variants
>>> of PVC).
>>
>> I misread this patch and thought it was an impossible condition that was
>> already protected during event init and it was added more as an "assert
>> we always have this". Now I see this is the call that actually protects
>> the event creation. So, yes, this looks the correct thing to do.
>>
>> Riana, could you expand the commit message to emphasize this is a real
>> issue for platforms like PVC?
Sure will do that.
>>
>> Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>
Thank you for the review
>>
>> thanks
>> Lucas De Marchi
>
> I did just notice (as Karthik also pointed out on another part of this
> thread) that if we apply this patch _without_ my series, then
> xe_device_get_gt() could throw a WARN and return something non-NULL if
> the GT ID is too high, which doesn't actually help. But if we apply
> this fix after my refactoring, then xe_device_get_gt() will return NULL
> on any invalid GT ID and the logic here works as expected. So I guess
> rather than applying this on its own, we could wait and apply it after
> my series (and I'd drop the patch #1 that I had added to v4 of my
> series).
>
I misread Karthik's comment. Yeah makes sense. I will wait
and apply after your series.
Thanks
Riana
>
> Matt
>
next prev parent reply other threads:[~2025-07-02 4:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 9:37 [PATCH] drm/xe/xe_pmu: Validate gt in event supported Riana Tauro
2025-06-30 15:33 ` Poosa, Karthik
2025-06-30 16:32 ` Riana Tauro
2025-06-30 22:28 ` [PATCH] " Lucas De Marchi
2025-07-01 5:08 ` Riana Tauro
2025-07-01 20:31 ` Matt Roper
2025-07-01 21:09 ` Lucas De Marchi
2025-07-01 21:19 ` Matt Roper
2025-07-02 4:54 ` Riana Tauro [this message]
2025-06-30 23:49 ` ✓ CI.KUnit: success for " Patchwork
2025-07-01 0:42 ` ✓ Xe.CI.BAT: " Patchwork
2025-07-02 11:00 ` ✓ Xe.CI.Full: " Patchwork
2025-07-02 23:16 ` Matt Roper
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=d524d82e-00dd-4881-82a1-1ffcea682138@intel.com \
--to=riana.tauro@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=karthik.poosa@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=sk.anirban@intel.com \
--cc=soham.purkait@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