From: Raag Jadav <raag.jadav@intel.com>
To: Matthew Brost <matthew.brost@intel.com>
Cc: lucas.demarchi@intel.com, rodrigo.vivi@intel.com,
intel-xe@lists.freedesktop.org, riana.tauro@intel.com,
daniele.ceraolospurio@intel.com, michal.wajdeczko@intel.com,
badal.nilawar@intel.com
Subject: Re: [PATCH v6 1/4] drm/xe/vf: Update pause/unpause() helpers with VF naming
Date: Wed, 22 Oct 2025 19:01:31 +0200 [thread overview]
Message-ID: <aPkN69Ulm-b5UJNa@black.igk.intel.com> (raw)
In-Reply-To: <aPj3AgztiXKC+iRY@lstrano-desk.jf.intel.com>
On Wed, Oct 22, 2025 at 08:23:46AM -0700, Matthew Brost wrote:
> On Wed, Oct 22, 2025 at 03:12:43PM +0530, Raag Jadav wrote:
> > Now that pause/unpause() helpers have been updated for VF migration
> > usecase, update their naming to match the functionality.
...
> > /**
> > - * xe_guc_submit_pause - Stop further runs of submission tasks on given GuC.
> > + * xe_guc_submit_vf_pause - Stop further runs of submission tasks for VF.
> > * @guc: the &xe_guc struct instance whose scheduler is to be disabled
> > */
> > -void xe_guc_submit_pause(struct xe_guc *guc)
> > +void xe_guc_submit_vf_pause(struct xe_guc *guc)
> > {
> > struct xe_exec_queue *q;
> > unsigned long index;
>
> Can we now have xe_gt_assert in the renamed functions that IS_SRIOV_VF
> is true?
I thought vf_recovery() already does it for us?
> Feel free add those in next rev and retain:
>
> Reviewed-by: Matthew Brost <matthew.brost@intel.com>
Thank you.
Raag
next prev parent reply other threads:[~2025-10-22 17:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 9:42 [PATCH v6 0/4] Introduce GT runtime suspend/resume Raag Jadav
2025-10-22 9:42 ` [PATCH v6 1/4] drm/xe/vf: Update pause/unpause() helpers with VF naming Raag Jadav
2025-10-22 15:23 ` Matthew Brost
2025-10-22 17:01 ` Raag Jadav [this message]
2025-10-22 17:16 ` Matthew Brost
2025-10-22 15:29 ` Michal Wajdeczko
2025-10-22 9:42 ` [PATCH v6 2/4] drm/xe/guc_submit: Bring back pause/unpause() helpers Raag Jadav
2025-10-22 15:31 ` Matthew Brost
2025-10-22 9:42 ` [PATCH v6 3/4] drm/xe/pm: Assert on runtime suspend if VFs are enabled Raag Jadav
2025-10-22 9:42 ` [PATCH v6 4/4] drm/xe/gt: Introduce runtime suspend/resume Raag Jadav
2025-10-22 15:38 ` Matthew Brost
2025-10-22 12:36 ` ✓ CI.KUnit: success for Introduce GT runtime suspend/resume (rev4) Patchwork
2025-10-22 14:00 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-10-22 15:38 ` ✗ Xe.CI.Full: " 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=aPkN69Ulm-b5UJNa@black.igk.intel.com \
--to=raag.jadav@intel.com \
--cc=badal.nilawar@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.brost@intel.com \
--cc=michal.wajdeczko@intel.com \
--cc=riana.tauro@intel.com \
--cc=rodrigo.vivi@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