From: "Piotr Piórkowski" <piotr.piorkowski@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe/pf: Fix VF's scheduling priority reporting
Date: Thu, 16 Apr 2026 18:06:00 +0200 [thread overview]
Message-ID: <20260416160600.lghjvz2avpgmxhse@intel.com> (raw)
In-Reply-To: <20260416131831.7302-1-michal.wajdeczko@intel.com>
Michal Wajdeczko <michal.wajdeczko@intel.com> wrote on czw [2026-kwi-16 15:18:31 +0200]:
> When preparing number of impacted VFs parameter for the reporting
> helper function, we wrongly ended with adding +1 (representing PF)
> twice, since local variable total_vfs was already adjusted. This
> resulted in printing a message that was referring to an invalid VF:
>
> [] xe ... [drm] PF: Enabled 2 of 24 VFs
> [] xe ... [drm] PF: Tile0: GT0: PF..VF25 provisioned with 0(low) scheduling priority
>
> Fix variable initialization and adjust the loop accordingly.
>
> Fixes: fbbf73a81b84 ("drm/xe/pf: Force new VFs prorities only once")
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
Reviewed-by: Piotr Piórkowski <piotr.piorkowski@intel.com>
> ---
> drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c b/drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c
> index e112aa148dab..2c9b85b84b1b 100644
> --- a/drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c
> +++ b/drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c
> @@ -2626,14 +2626,14 @@ u32 xe_gt_sriov_pf_config_get_sched_priority(struct xe_gt *gt, unsigned int vfid
> */
> void xe_gt_sriov_pf_config_force_sched_priority_locked(struct xe_gt *gt, u32 priority)
> {
> - unsigned int total_vfs = 1 + xe_gt_sriov_pf_get_totalvfs(gt);
> + unsigned int total_vfs = xe_gt_sriov_pf_get_totalvfs(gt);
> struct xe_gt_sriov_config *config;
> unsigned int n;
>
> xe_gt_assert(gt, IS_SRIOV_PF(gt_to_xe(gt)));
> lockdep_assert_held(xe_gt_sriov_pf_master_mutex(gt));
>
> - for (n = 0; n < total_vfs; n++) {
> + for (n = 0; n <= total_vfs; n++) {
> config = pf_pick_vf_config(gt, VFID(n));
> config->sched_priority = priority;
> }
> --
> 2.47.1
>
--
prev parent reply other threads:[~2026-04-16 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 13:18 [PATCH] drm/xe/pf: Fix VF's scheduling priority reporting Michal Wajdeczko
2026-04-16 13:24 ` ✗ CI.checkpatch: warning for " Patchwork
2026-04-16 13:26 ` ✓ CI.KUnit: success " Patchwork
2026-04-16 14:32 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-16 15:36 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-16 21:24 ` Michal Wajdeczko
2026-04-16 16:06 ` Piotr Piórkowski [this message]
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=20260416160600.lghjvz2avpgmxhse@intel.com \
--to=piotr.piorkowski@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=michal.wajdeczko@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