From: "Ghimiray, Himal Prasad" <himal.prasad.ghimiray@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 1/2] drm/xe/vf: Don't try Driver-FLR if VF
Date: Tue, 11 Mar 2025 19:55:12 +0530 [thread overview]
Message-ID: <0af001ae-1e86-43ea-849f-30213936ec14@intel.com> (raw)
In-Reply-To: <20250311135726.1998-2-michal.wajdeczko@intel.com>
On 11-03-2025 19:27, Michal Wajdeczko wrote:
> Driver-FLR can't be triggered from the VF driver, so treat it
> as disabled if VF. While around, fix also the message, as it
> shouldn't be printed just 'once' as we may have many devices.
>
does it need fixes tag ?
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> ---
> drivers/gpu/drm/xe/xe_device.c | 14 ++++++++++----
> 1 file changed, 10 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_device.c b/drivers/gpu/drm/xe/xe_device.c
> index 5d79b439dd62..a2afa8a88997 100644
> --- a/drivers/gpu/drm/xe/xe_device.c
> +++ b/drivers/gpu/drm/xe/xe_device.c
> @@ -504,7 +504,15 @@ ALLOW_ERROR_INJECTION(xe_device_create, ERRNO); /* See xe_pci_probe() */
>
> static bool xe_driver_flr_disabled(struct xe_device *xe)
> {
> - return xe_mmio_read32(xe_root_tile_mmio(xe), GU_CNTL_PROTECTED) & DRIVERINT_FLR_DIS;
> + if (IS_SRIOV_VF(xe))
> + return true;
> +
> + if (xe_mmio_read32(xe_root_tile_mmio(xe), GU_CNTL_PROTECTED) & DRIVERINT_FLR_DIS) {
> + drm_info(&xe->drm, "Driver-FLR disabled by BIOS\n");
> + return true;
> + }
> +
> + return false;
> }
>
> /*
> @@ -568,10 +576,8 @@ static void __xe_driver_flr(struct xe_device *xe)
>
> static void xe_driver_flr(struct xe_device *xe)
> {
> - if (xe_driver_flr_disabled(xe)) {
> - drm_info_once(&xe->drm, "BIOS Disabled Driver-FLR\n");
> + if (xe_driver_flr_disabled(xe))
> return;
> - }
Change LGTM
Reviewed-by: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
>
> __xe_driver_flr(xe);
> }
next prev parent reply other threads:[~2025-03-11 14:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 13:57 [PATCH 0/2] VF: Catch all unexpected registers accesses Michal Wajdeczko
2025-03-11 13:57 ` [PATCH 1/2] drm/xe/vf: Don't try Driver-FLR if VF Michal Wajdeczko
2025-03-11 14:25 ` Ghimiray, Himal Prasad [this message]
2025-03-11 15:15 ` Michal Wajdeczko
2025-03-11 18:02 ` Matt Roper
2025-03-11 13:57 ` [PATCH 2/2] drm/xe/vf: Catch all unexpected register reads Michal Wajdeczko
2025-03-11 14:23 ` Ghimiray, Himal Prasad
2025-03-11 15:27 ` Michal Wajdeczko
2025-03-11 18:08 ` Matt Roper
2025-03-11 15:20 ` ✓ CI.Patch_applied: success for VF: Catch all unexpected registers accesses Patchwork
2025-03-11 15:20 ` ✓ CI.checkpatch: " Patchwork
2025-03-11 15:21 ` ✓ CI.KUnit: " Patchwork
2025-03-11 15:38 ` ✓ CI.Build: " Patchwork
2025-03-11 15:40 ` ✓ CI.Hooks: " Patchwork
2025-03-11 15:42 ` ✓ CI.checksparse: " Patchwork
2025-03-11 16:02 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-12 7:41 ` ✓ 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=0af001ae-1e86-43ea-849f-30213936ec14@intel.com \
--to=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
/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