From: Raag Jadav <raag.jadav@intel.com>
To: Sk Anirban <sk.anirban@intel.com>, lucas.demarchi@intel.com
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 4/12] drm/xe/cri: Add new performance limit reasons bits
Date: Wed, 22 Oct 2025 08:31:39 +0200 [thread overview]
Message-ID: <aPh6S_8bv345QPR0@black.igk.intel.com> (raw)
In-Reply-To: <20251021-cri-v1-4-bf11e61d9f49@intel.com>
On Tue, Oct 21, 2025 at 10:17:36PM -0700, Sk Anirban wrote:
> Add support for additional performance limit reasons in
> GT0_PERF_LIMIT_REASONS register.
>
> Signed-off-by: Sk Anirban <sk.anirban@intel.com>
> ---
> There are some improvements to be made here before applying to reduce
> the amount of code for one platform. I plan to take a look on that for
> v2.
Yes, I had planned this but there were some concerns related to backporting
(in case there arises such a requirement). I'll leave the final call to you.
Raag
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
> ---
next prev parent reply other threads:[~2025-10-22 6:31 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 5:17 [PATCH 00/12] drm/xe: Add support for Crescent Island Lucas De Marchi
2025-10-22 5:17 ` [PATCH 01/12] drm/xe/cri: Add CRI platform definition Lucas De Marchi
2025-10-22 14:58 ` Shekhar Chauhan
2025-10-22 19:45 ` Lucas De Marchi
2025-10-23 10:57 ` Lucas De Marchi
2025-10-23 11:13 ` Lucas De Marchi
2025-10-22 5:17 ` [PATCH 02/12] topic/for-xe-CI: drm/xe/cri: Define GuC firmware for CRI Lucas De Marchi
2025-10-23 10:33 ` Lucas De Marchi
2025-10-22 5:17 ` [PATCH 03/12] drm/xe/cri: Setup MOCS table Lucas De Marchi
2025-10-22 8:06 ` Vivekanandan, Balasubramani
2025-10-22 5:17 ` [PATCH 04/12] drm/xe/cri: Add new performance limit reasons bits Lucas De Marchi
2025-10-22 6:31 ` Raag Jadav [this message]
2025-10-22 21:22 ` [PATCH 4/12] " Lucas De Marchi
2025-10-22 5:17 ` [PATCH 05/12] drm/xe/cri: Add check to verify if CSC is a PCIe endpoint Lucas De Marchi
2025-10-22 5:17 ` [PATCH 06/12] drm/xe/pm: Enable D3cold WAKE# support Lucas De Marchi
2025-10-22 6:35 ` [PATCH 6/12] " Raag Jadav
2025-10-22 19:53 ` Lucas De Marchi
2025-10-22 5:17 ` [PATCH 07/12] drm/xe: Add device flag to indicate standalone MERT Lucas De Marchi
2025-10-28 21:53 ` Dixit, Ashutosh
2025-10-22 5:17 ` [PATCH 08/12] drm/xe/oa/uapi: Expose MERT OA unit Lucas De Marchi
2025-10-22 23:09 ` Umesh Nerlige Ramappa
2025-11-24 21:34 ` Dixit, Ashutosh
2025-10-22 5:17 ` [PATCH 09/12] drm/xe/pf: Configure LMTT in MERT Lucas De Marchi
2025-10-22 5:17 ` [PATCH 10/12] drm/xe: Handle MERT interrupts Lucas De Marchi
2025-10-22 23:19 ` Matt Roper
2025-10-23 14:42 ` Lucas De Marchi
2025-10-28 9:30 ` Laguna, Lukasz
2025-10-22 5:17 ` [PATCH 11/12] drm/xe/pf: Add TLB invalidation support for MERT Lucas De Marchi
2025-10-22 18:28 ` Matthew Brost
2025-10-23 15:11 ` Lucas De Marchi
2025-10-28 9:33 ` Laguna, Lukasz
2025-10-22 5:17 ` [PATCH 12/12] drm/xe/pf: Handle MERT catastrophic errors Lucas De Marchi
2025-10-22 5:40 ` ✗ CI.checkpatch: warning for drm/xe: Add support for Crescent Island Patchwork
2025-10-22 5:41 ` ✓ CI.KUnit: success " Patchwork
2025-10-22 6:29 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-22 7:56 ` ✗ Xe.CI.Full: 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=aPh6S_8bv345QPR0@black.igk.intel.com \
--to=raag.jadav@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=sk.anirban@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