From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>,
intel-gfx@lists.freedesktop.org,
intel-gvt-dev@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/i915: Fix GVT-g PVINFO version compatibility check
Date: Thu, 08 Jun 2017 12:17:01 +0300 [thread overview]
Message-ID: <1496913421.2924.2.camel@linux.intel.com> (raw)
In-Reply-To: <20170608065824.3060-1-zhenyuw@linux.intel.com>
On to, 2017-06-08 at 14:58 +0800, Zhenyu Wang wrote:
> Current it's strictly checked if PVINFO version matches 1.0
> for GVT-g i915 guest which doesn't help for compatibility at
> all and forces GVT-g host can't extend PVINFO easily with version
> bump for real compatibility check.
>
> This fixes that to check minimal required PVINFO version instead.
>
> v2:
> - drop unneeded version macro
> - use only major version for sanity check
>
> Cc: Chuanxiao Dong <chuanxiao.dong@intel.com>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: stable@vger.kernel.org # v4.10+
> Signed-off-by: Zhenyu Wang <zhenyuw@linux.intel.com>
<SNIP>
> +++ b/drivers/gpu/drm/i915/i915_vgpu.c
> @@ -61,7 +61,7 @@
> void i915_check_vgpu(struct drm_i915_private *dev_priv)
> {
> uint64_t magic;
> - uint32_t version;
> + uint32_t version_major;
Just a final tune, change these types into u64 and u32 respectively.
>
> BUILD_BUG_ON(sizeof(struct vgt_if) != VGT_PVINFO_SIZE);
>
> @@ -69,10 +69,9 @@ void i915_check_vgpu(struct drm_i915_private *dev_priv)
> if (magic != VGT_MAGIC)
> return;
>
> - version = INTEL_VGT_IF_VERSION_ENCODE(
> - __raw_i915_read16(dev_priv, vgtif_reg(version_major)),
> - __raw_i915_read16(dev_priv, vgtif_reg(version_minor)));
> - if (version != INTEL_VGT_IF_VERSION) {
> + version_major = __raw_i915_read16(dev_priv,
> + vgtif_reg(version_major));
This assignment fits a single line now.
Then this is;
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-06-08 9:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 3:00 [PATCH] drm/i915: Fix GVT-g PVINFO version compatibility check Zhenyu Wang
2017-06-05 3:25 ` ✗ Fi.CI.BAT: warning for " Patchwork
2017-06-05 13:40 ` [PATCH] " Joonas Lahtinen
2017-06-07 9:16 ` Zhenyu Wang
2017-06-08 6:58 ` [PATCH v2] " Zhenyu Wang
2017-06-08 9:17 ` Joonas Lahtinen [this message]
2017-06-09 7:48 ` [PATCH v3] " Zhenyu Wang
2017-06-08 7:27 ` ✓ Fi.CI.BAT: success for drm/i915: Fix GVT-g PVINFO version compatibility check (rev2) Patchwork
2017-06-09 8:10 ` ✓ Fi.CI.BAT: success for drm/i915: Fix GVT-g PVINFO version compatibility check (rev3) Patchwork
2017-06-12 12:46 ` Joonas Lahtinen
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=1496913421.2924.2.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=zhenyuw@linux.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