From: "Piotr Piórkowski" <piotr.piorkowski@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Nirmoy Das <nirmoy.das@intel.com>
Subject: Re: [PATCH] drm/xe/vf: Use correct check for being a VF driver
Date: Thu, 13 Jun 2024 14:14:47 +0200 [thread overview]
Message-ID: <20240613121447.jgpccepgovixmepi@intel.com> (raw)
In-Reply-To: <20240613120749.2032-1-michal.wajdeczko@intel.com>
Michal Wajdeczko <michal.wajdeczko@intel.com> wrote on czw [2024-cze-13 14:07:49 +0200]:
> The IS_SRIOV macro returns true also when we are running as a PF
> driver. Use correct IS_SRIOV_VF macro to skip force-wake management.
>
> Fixes: 513ea833c201 ("drm/xe/vf: Ignore force-wake requests if VF")
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Piotr Piórkowski <piotr.piorkowski@intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: Nirmoy Das <nirmoy.das@intel.com>
> ---
> drivers/gpu/drm/xe/xe_force_wake.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_force_wake.c b/drivers/gpu/drm/xe/xe_force_wake.c
> index 5db6926120c3..b263fff15273 100644
> --- a/drivers/gpu/drm/xe/xe_force_wake.c
> +++ b/drivers/gpu/drm/xe/xe_force_wake.c
> @@ -97,7 +97,7 @@ void xe_force_wake_init_engines(struct xe_gt *gt, struct xe_force_wake *fw)
>
> static void __domain_ctl(struct xe_gt *gt, struct xe_force_wake_domain *domain, bool wake)
> {
> - if (IS_SRIOV(gt_to_xe(gt)))
> + if (IS_SRIOV_VF(gt_to_xe(gt)))
> return;
>
> xe_mmio_write32(gt, domain->reg_ctl, domain->mask | (wake ? domain->val : 0));
> @@ -108,7 +108,7 @@ static int __domain_wait(struct xe_gt *gt, struct xe_force_wake_domain *domain,
> u32 value;
> int ret;
>
> - if (IS_SRIOV(gt_to_xe(gt)))
> + if (IS_SRIOV_VF(gt_to_xe(gt)))
> return 0;
>
> ret = xe_mmio_wait32(gt, domain->reg_ack, domain->val, wake ? domain->val : 0,
Reviewed-by: Piotr Piórkowski <piotr.piorkowski@intel.com>
> --
> 2.43.0
>
--
next prev parent reply other threads:[~2024-06-13 12:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 12:07 [PATCH] drm/xe/vf: Use correct check for being a VF driver Michal Wajdeczko
2024-06-13 12:14 ` Piotr Piórkowski [this message]
2024-06-13 13:00 ` ✓ CI.Patch_applied: success for " Patchwork
2024-06-13 13:00 ` ✓ CI.checkpatch: " Patchwork
2024-06-13 13:02 ` ✓ CI.KUnit: " Patchwork
2024-06-13 13:14 ` ✓ CI.Build: " Patchwork
2024-06-13 13:16 ` ✗ CI.Hooks: failure " Patchwork
2024-06-13 13:17 ` ✓ CI.checksparse: success " Patchwork
2024-06-13 13:34 ` [PATCH] " Nirmoy Das
2024-06-13 13:52 ` ✓ CI.BAT: success for " Patchwork
2024-06-13 18:12 ` ✓ 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=20240613121447.jgpccepgovixmepi@intel.com \
--to=piotr.piorkowski@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=michal.wajdeczko@intel.com \
--cc=nirmoy.das@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