From: Jani Nikula <jani.nikula@intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
intel-gvt-dev <intel-gvt-dev@lists.freedesktop.org>,
"Lv, Zhiyuan" <zhiyuan.lv@intel.com>,
"Yuan, Hang" <hang.yuan@intel.com>
Subject: Re: [PULL] gvt-fixes
Date: Wed, 19 Jun 2019 10:56:08 +0300 [thread overview]
Message-ID: <877e9im2jr.fsf@intel.com> (raw)
In-Reply-To: <20190619062240.GM9684@zhen-hp.sh.intel.com>
On Wed, 19 Jun 2019, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
> Hi,
>
> Here's one gvt fix for 5.2-rc6 to sanitize reserved register write in
> PVINFO which should be discarded. This fixed some guest behavior which
> contain some unmerged features that probe through PVINFO register state.
>
> Thanks.
Pulled to drm-intel-fixes, thanks.
BR,
Jani.
> --
> The following changes since commit 15e7f52a4596b496ce3da2fa4c1f94c6fb0023f2:
>
> drm/i915/gvt: save RING_HEAD into vreg when vgpu switched out (2019-06-03 13:18:36 +0800)
>
> are available in the Git repository at:
>
> https://github.com/intel/gvt-linux tags/gvt-fixes-2019-06-19
>
> for you to fetch changes up to 971afec3a5373f96684ad899579f6a4d51462410:
>
> drm/i915/gvt: ignore unexpected pvinfo write (2019-06-17 15:45:41 +0800)
>
> ----------------------------------------------------------------
> gvt-fixes-2019-06-19
>
> - Fix reserved PVINFO register write (Weinan)
>
> ----------------------------------------------------------------
> Weinan Li (1):
> drm/i915/gvt: ignore unexpected pvinfo write
>
> drivers/gpu/drm/i915/gvt/handlers.c | 15 +++++++++------
> 1 file changed, 9 insertions(+), 6 deletions(-)
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-06-19 7:56 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 6:22 [PULL] gvt-fixes Zhenyu Wang
2019-06-19 7:56 ` Jani Nikula [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-31 9:38 Zhenyu Wang
2024-02-01 14:44 ` Joonas Lahtinen
2024-02-05 3:21 ` Zhenyu Wang
2019-11-22 3:33 Zhenyu Wang
2019-11-12 6:18 Zhenyu Wang
2019-11-12 20:36 ` Vivi, Rodrigo
2019-08-13 9:58 Zhenyu Wang
2019-08-13 13:41 ` Jani Nikula
2019-07-23 9:29 Zhenyu Wang
2019-07-29 3:33 ` Zhenyu Wang
2019-07-29 11:05 ` Jani Nikula
2019-07-30 7:00 ` Zhenyu Wang
2019-07-30 8:33 ` Jani Nikula
2019-06-05 8:49 Zhenyu Wang
2019-06-06 12:04 ` Joonas Lahtinen
2019-05-29 9:06 Zhenyu Wang
2019-05-29 12:07 ` Joonas Lahtinen
2019-05-30 3:41 ` Zhenyu Wang
2019-05-31 8:16 ` Joonas Lahtinen
2019-05-21 6:24 Zhenyu Wang
2019-05-21 12:35 ` Joonas Lahtinen
2019-04-11 6:49 Zhenyu Wang
2019-04-11 16:48 ` Rodrigo Vivi
2019-04-02 9:40 Zhenyu Wang
2019-04-04 0:12 ` Rodrigo Vivi
2019-04-04 0:32 ` Zhenyu Wang
2019-04-04 1:03 ` Rodrigo Vivi
2019-04-04 0:39 ` Zhenyu Wang
2019-03-21 3:50 Zhenyu Wang
2019-03-21 20:03 ` Rodrigo Vivi
2019-01-24 5:48 Zhenyu Wang
2019-01-31 9:45 ` Jani Nikula
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=877e9im2jr.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=hang.yuan@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=zhenyuw@linux.intel.com \
--cc=zhiyuan.lv@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.