Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Nilawar, Badal" <badal.nilawar@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
	<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 6/8] drm/xe/vf: Don't enable hwmon if VF
Date: Wed, 17 Jan 2024 01:34:08 +0530	[thread overview]
Message-ID: <bf5627bc-3388-467d-8589-286e816337ef@intel.com> (raw)
In-Reply-To: <20240112152649.849-7-michal.wajdeczko@intel.com>



On 12-01-2024 20:56, Michal Wajdeczko wrote:
> Registers used by hwmon are not available for VF drivers.
> 
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Badal Nilawar <badal.nilawar@intel.com>
> ---
>   drivers/gpu/drm/xe/xe_hwmon.c | 5 +++++
>   1 file changed, 5 insertions(+)
> 
> diff --git a/drivers/gpu/drm/xe/xe_hwmon.c b/drivers/gpu/drm/xe/xe_hwmon.c
> index 6ef2aa1eae8b..9848bf84b58b 100644
> --- a/drivers/gpu/drm/xe/xe_hwmon.c
> +++ b/drivers/gpu/drm/xe/xe_hwmon.c
> @@ -16,6 +16,7 @@
>   #include "xe_mmio.h"
>   #include "xe_pcode.h"
>   #include "xe_pcode_api.h"
> +#include "xe_sriov.h"
>   
>   enum xe_hwmon_reg {
>   	REG_PKG_RAPL_LIMIT,
> @@ -745,6 +746,10 @@ void xe_hwmon_register(struct xe_device *xe)
>   	if (!IS_DGFX(xe))
>   		return;
>   
> +	/* hwmon is not available on VFs */
> +	if (IS_SRIOV_VF(xe))
> +		return;
Reviewed-by: Badal Nilawar <badal.nilawar@intel.com>
> +
>   	hwmon = devm_kzalloc(dev, sizeof(*hwmon), GFP_KERNEL);
>   	if (!hwmon)
>   		return;

  reply	other threads:[~2024-01-16 20:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-12 15:26 [PATCH 0/8] VF Tweaks Michal Wajdeczko
2024-01-12 15:26 ` [PATCH 1/8] drm/xe/vf: Assume fixed GSM size if VF Michal Wajdeczko
2024-01-13  1:13   ` Matt Roper
2024-01-12 15:26 ` [PATCH 2/8] drm/xe/vf: Don't try to capture engine data unavailable to VF Michal Wajdeczko
2024-01-12 21:15   ` Rodrigo Vivi
2024-01-12 15:26 ` [PATCH 3/8] drm/xe/vf: Don't program MOCS if VF Michal Wajdeczko
2024-01-13  0:54   ` Matt Roper
2024-01-12 15:26 ` [PATCH 4/8] drm/xe/vf: Don't initialize stolen memory manager " Michal Wajdeczko
2024-02-06 17:47   ` Matt Roper
2024-01-12 15:26 ` [PATCH 5/8] drm/xe/vf: Don't check if LMEM is initialized " Michal Wajdeczko
2024-01-13  4:37   ` Matt Roper
2024-01-12 15:26 ` [PATCH 6/8] drm/xe/vf: Don't enable hwmon " Michal Wajdeczko
2024-01-16 20:04   ` Nilawar, Badal [this message]
2024-01-12 15:26 ` [PATCH 7/8] drm/xe/vf: Don't program PAT " Michal Wajdeczko
2024-01-13  0:56   ` Matt Roper
2024-01-12 15:26 ` [PATCH 8/8] drm/xe/vf: Don't support MCR registers " Michal Wajdeczko
2024-01-13  1:11   ` Matt Roper
2024-01-12 15:30 ` ✓ CI.Patch_applied: success for VF Tweaks Patchwork
2024-01-12 15:30 ` ✓ CI.checkpatch: " Patchwork
2024-01-12 15:31 ` ✓ CI.KUnit: " Patchwork
2024-01-12 15:38 ` ✓ CI.Build: " Patchwork
2024-01-12 15:38 ` ✓ CI.Hooks: " Patchwork
2024-01-12 15:40 ` ✓ CI.checksparse: " Patchwork
2024-01-12 16:03 ` ✓ CI.BAT: " 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=bf5627bc-3388-467d-8589-286e816337ef@intel.com \
    --to=badal.nilawar@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