From: Matt Roper <matthew.d.roper@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Riana Tauro <riana.tauro@intel.com>,
<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: Tue, 1 Jul 2025 13:31:28 -0700 [thread overview]
Message-ID: <20250701203128.GL4868@mdroper-desk1.amr.corp.intel.com> (raw)
In-Reply-To: <q7bmmb7s3v2wxjeamrcuhcpwm23tlju2l3uqobg3mo4y47dj5r@ndr2kbjfhhkc>
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).
So we should either land this patch first (which will remove a hunk from
one of my patches), or make this as a separate change on top of my
series. In the latest version of my series (v4) I included a patch
identical to this one as patch #1 since I didn't notice that this patch
was exactly the same thing; if this one lands, then we can drop the
first one from v4 of my series.
Matt
>
> Lucas De Marchi
--
Matt Roper
Graphics Software Engineer
Linux GPU Platform Enablement
Intel Corporation
next prev parent reply other threads:[~2025-07-01 20:32 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 [this message]
2025-07-01 21:09 ` Lucas De Marchi
2025-07-01 21:19 ` Matt Roper
2025-07-02 4:54 ` Riana Tauro
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=20250701203128.GL4868@mdroper-desk1.amr.corp.intel.com \
--to=matthew.d.roper@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=riana.tauro@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