From: Raag Jadav <raag.jadav@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 4/5] drm/xe/gt_throttle: Add throttle_to_gt()
Date: Fri, 24 Oct 2025 10:15:08 +0200 [thread overview]
Message-ID: <aPs1jPILbBBUTICW@black.igk.intel.com> (raw)
In-Reply-To: <20251023-gt-throttle-cri-v1-4-9f36f3c8861c@intel.com>
On Thu, Oct 23, 2025 at 09:56:57AM -0700, Lucas De Marchi wrote:
> Reduce boilerplate code by adding a helper to go directly from the
> throttle kobject to the gt. Note that there's already a kobj_to_gt(),
> but that actually converts our kobj_gt object to gt.
Nice. These usually get me confused about where we are.
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
Reviewed-by: Raag Jadav <raag.jadav@intel.com>
next prev parent reply other threads:[~2025-10-24 8:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 16:56 [PATCH 0/5] drm/xe: CRI support in gt_throttle + refactors Lucas De Marchi
2025-10-23 16:56 ` [PATCH 1/5] drm/xe/cri: Add new performance limit reasons bits Lucas De Marchi
2025-10-24 5:55 ` Raag Jadav
2025-10-23 16:56 ` [PATCH 2/5] drm/xe/gt_throttle: Tidy up perf reasons reading Lucas De Marchi
2025-10-24 5:59 ` Raag Jadav
2025-10-23 16:56 ` [PATCH 3/5] drm/xe/gt_throttle: Always read and mask Lucas De Marchi
2025-10-24 6:13 ` Raag Jadav
2025-10-24 16:13 ` Lucas De Marchi
2025-10-25 15:46 ` Raag Jadav
2025-10-23 16:56 ` [PATCH 4/5] drm/xe/gt_throttle: Add throttle_to_gt() Lucas De Marchi
2025-10-24 8:15 ` Raag Jadav [this message]
2025-10-23 16:56 ` [PATCH 5/5] drm/xe/gt_throttle: Tidy up attribute definition Lucas De Marchi
2025-10-24 8:34 ` Raag Jadav
2025-10-23 19:29 ` ✗ CI.checkpatch: warning for drm/xe: CRI support in gt_throttle + refactors Patchwork
2025-10-23 19:31 ` ✓ CI.KUnit: success " Patchwork
2025-10-23 20:32 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-24 8:42 ` ✗ 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=aPs1jPILbBBUTICW@black.igk.intel.com \
--to=raag.jadav@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.