From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
"Yuan, Hang" <hang.yuan@intel.com>,
"Lv, Zhiyuan" <zhiyuan.lv@intel.com>,
intel-gvt-dev <intel-gvt-dev@lists.freedesktop.org>
Subject: Re: [PULL] gvt-fixes for 4.19-rc4
Date: Mon, 10 Sep 2018 12:43:46 -0700 [thread overview]
Message-ID: <20180910194346.GC8001@intel.com> (raw)
In-Reply-To: <20180910092212.GZ20737@zhen-hp.sh.intel.com>
Pulled, thanks!
On Mon, Sep 10, 2018 at 05:22:12PM +0800, Zhenyu Wang wrote:
>
> Hi,
>
> Here's more gvt-fixes for 4.19. Most critical one is to fix
> KVM's mm reference when we access guest memory, issue was raised
> by Linus in https://lists.freedesktop.org/archives/intel-gvt-dev/2018-August/004130.html.
> Another one with virtual opregion fix.
>
> Thanks
> --
> The following changes since commit 54ff01fd0d44b9681615f77c15fe9ea6dfadb501:
>
> drm/i915/gvt: Give new born vGPU higher scheduling chance (2018-09-03 14:28:23 +0800)
>
> are available in the Git repository at:
>
> https://github.com/intel/gvt-linux.git tags/gvt-fixes-2018-09-10
>
> for you to fetch changes up to 792fab2c0d45758ad3d187bd252570d2bb627fa9:
>
> drm/i915/gvt: Fix the incorrect length of child_device_config issue (2018-09-06 11:17:38 +0800)
>
> ----------------------------------------------------------------
> gvt-fixes-2018-09-10
>
> - KVM mm access reference fix (Zhenyu)
> - Fix child device config length for virtual opregion (Weinan)
>
> ----------------------------------------------------------------
> Weinan Li (1):
> drm/i915/gvt: Fix the incorrect length of child_device_config issue
>
> Zhenyu Wang (1):
> drm/i915/gvt: Fix life cycle reference on KVM mm
>
> drivers/gpu/drm/i915/gvt/kvmgt.c | 10 ++++++++--
> drivers/gpu/drm/i915/gvt/opregion.c | 20 +++++++++-----------
> 2 files changed, 17 insertions(+), 13 deletions(-)
>
> --
> Open Source Technology Center, Intel ltd.
>
> $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2018-09-10 19:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 9:22 [PULL] gvt-fixes for 4.19-rc4 Zhenyu Wang
2018-09-10 19:43 ` Rodrigo Vivi [this message]
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=20180910194346.GC8001@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=hang.yuan@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jani.nikula@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox