public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Nareshkumar Gollakoti <naresh.kumar.g@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: thomas.hellstrom@intel.com, tejas.upadhyay@intel.com,
	himal.prasad.ghimiray@intel.com,
	Nareshkumar Gollakoti <naresh.kumar.g@intel.com>
Subject: [PATCH 0/1] drm/xe: Set GT rp min frequency as 1.2GHz default for BMG/CRI
Date: Mon, 16 Feb 2026 19:21:08 +0530	[thread overview]
Message-ID: <20260216135107.3148167-3-naresh.kumar.g@intel.com> (raw)

Performance degradation occurs in multi-BMG GPU configurations 
during Peer-to-Peer transactions when one of the two GPUs remains idle
with no engine activity.
The root cause has been identified as frequency downscaling:
the idle remote GPU reduces its operating frequency to the minimum 400MHz,
which negatively impacts the bandwidth available for P2P transactions 
initiated by the active local GPU.

To address above problem this patch ensures for the platform BMG/CRI
the default GT rp frquency min set as 1.2GHz to ensure effetive P2P
transaction bandwidth.

Note: 
While frequency boosting improves performance, 
it also increases power consumption. In single GPU mode,
it causes the GPU to operate at unnecessarily high frequencies by default
and as of now we do not have any mechanism to limit this for single
GPU.

Nareshkumar Gollakoti (1):
  drm/xe: Set GT rp min frequency as 1.2GHz default for BMG/CRI

 drivers/gpu/drm/xe/xe_guc_pc.c | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

-- 
2.43.0


             reply	other threads:[~2026-02-16 13:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-16 13:51 Nareshkumar Gollakoti [this message]
2026-02-16 13:51 ` [PATCH 1/1] drm/xe: Set GT rp min frequency as 1.2GHz default for BMG/CRI Nareshkumar Gollakoti
2026-02-18  9:04   ` Hellstrom, Thomas
2026-02-20  9:06     ` Mrozek, Michal
2026-02-26  8:50     ` Kumar G, Naresh
2026-02-26 12:03   ` Hellstrom, Thomas
2026-02-26 22:36   ` Belgaumkar, Vinay
2026-02-26 23:37   ` Summers, Stuart
2026-02-27  0:30     ` Matt Roper
2026-03-03 13:41       ` Kumar G, Naresh
2026-02-16 14:17 ` [PATCH 0/1] " Hellstrom, Thomas
2026-02-16 14:40   ` Thomas Hellström
2026-02-16 15:17 ` ✓ CI.KUnit: success for " Patchwork
2026-02-16 16:03 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-16 20:48 ` ✗ 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=20260216135107.3148167-3-naresh.kumar.g@intel.com \
    --to=naresh.kumar.g@intel.com \
    --cc=himal.prasad.ghimiray@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=tejas.upadhyay@intel.com \
    --cc=thomas.hellstrom@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