All of lore.kernel.org
 help / color / mirror / Atom feed
From: Radhakrishna Sripada <radhakrishna.sripada@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, Zhi Wang <zhi.a.wang@intel.com>
Subject: Re: [PATCH 5/6] drm/i915/gvt: use local INTEL_GVT_OPREGION_SIZE
Date: Thu, 11 Jan 2024 16:15:16 -0800	[thread overview]
Message-ID: <ZaCElN5sBpe6g9Yr@invictus> (raw)
In-Reply-To: <8ae6e10fc0929934a14547a973312e82a4d7f7d1.1704992868.git.jani.nikula@intel.com>

On Thu, Jan 11, 2024 at 07:21:18PM +0200, Jani Nikula wrote:
> All of gvt uses INTEL_GVT_OPREGION_SIZE for opregion size. Follow suit
> here.
> 
> Cc: Zhenyu Wang <zhenyuw@linux.intel.com>
> Cc: Zhi Wang <zhi.a.wang@intel.com>
> Cc: Radhakrishna Sripada <radhakrishna.sripada@intel.com>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Radhakrishna Sripada <radhakrishna.sripada@intel.com>

> ---
>  drivers/gpu/drm/i915/gvt/kvmgt.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/gvt/kvmgt.c b/drivers/gpu/drm/i915/gvt/kvmgt.c
> index faf21be724c3..4f74d867fe1a 100644
> --- a/drivers/gpu/drm/i915/gvt/kvmgt.c
> +++ b/drivers/gpu/drm/i915/gvt/kvmgt.c
> @@ -574,7 +574,7 @@ int intel_gvt_set_opregion(struct intel_vgpu *vgpu)
>  	ret = intel_vgpu_register_reg(vgpu,
>  			PCI_VENDOR_ID_INTEL | VFIO_REGION_TYPE_PCI_VENDOR_TYPE,
>  			VFIO_REGION_SUBTYPE_INTEL_IGD_OPREGION,
> -			&intel_vgpu_regops_opregion, OPREGION_SIZE,
> +			&intel_vgpu_regops_opregion, INTEL_GVT_OPREGION_SIZE,
>  			VFIO_REGION_INFO_FLAG_READ, base);
>  
>  	return ret;
> -- 
> 2.39.2
> 

  reply	other threads:[~2024-01-12  0:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-11 17:21 [PATCH 0/6] drm/i915/opregion: better abstractions Jani Nikula
2024-01-11 17:21 ` [PATCH 1/6] drm/i915/bios: move i915_vbt debugfs to intel_bios.c Jani Nikula
2024-01-11 23:11   ` Radhakrishna Sripada
2024-01-11 17:21 ` [PATCH 2/6] drm/i915/opregion: move i915_opregion debugfs to intel_opregion.c Jani Nikula
2024-01-11 23:20   ` Radhakrishna Sripada
2024-01-11 17:21 ` [PATCH 3/6] drm/i915/opregion: abstract getting the opregion VBT Jani Nikula
2024-01-11 23:22   ` Radhakrishna Sripada
2024-01-11 17:21 ` [PATCH 4/6] drm/i915/opregion: abstract ASLE presence check Jani Nikula
2024-01-12  0:03   ` Radhakrishna Sripada
2024-01-12 10:17     ` Jani Nikula
2024-01-12 19:36       ` Radhakrishna Sripada
2024-01-15 13:48         ` Jani Nikula
2024-01-16  9:57           ` Jani Nikula
2024-01-11 17:21 ` [PATCH 5/6] drm/i915/gvt: use local INTEL_GVT_OPREGION_SIZE Jani Nikula
2024-01-12  0:15   ` Radhakrishna Sripada [this message]
2024-01-11 17:21 ` [PATCH 6/6] drm/i915/opregion: make struct intel_opregion opaque Jani Nikula
2024-01-12  0:13   ` Radhakrishna Sripada
2024-01-17 11:25   ` Ville Syrjälä
2024-01-17 12:43     ` Jani Nikula
2024-01-11 18:19 ` ✗ Fi.CI.SPARSE: warning for drm/i915/opregion: better abstractions Patchwork
2024-01-11 18:37 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-01-15 14:14 ` ✗ Fi.CI.SPARSE: warning for drm/i915/opregion: better abstractions (rev2) Patchwork
2024-01-15 14:26 ` ✓ Fi.CI.BAT: success " Patchwork
2024-01-15 16:55 ` ✗ Fi.CI.IGT: failure " 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=ZaCElN5sBpe6g9Yr@invictus \
    --to=radhakrishna.sripada@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=zhi.a.wang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.