From: Jani Nikula <jani.nikula@intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@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 for 5.0-rc3
Date: Thu, 17 Jan 2019 12:16:14 +0200 [thread overview]
Message-ID: <87h8e7fv2p.fsf@intel.com> (raw)
In-Reply-To: <20190117074604.GI18272@zhen-hp.sh.intel.com>
On Thu, 17 Jan 2019, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
> Hi,
>
> This contains one cmd parser failure fix to allow cmd access
> for one register, and fix region cleanup properly in vGPU destroy,
> and another fix for critical mmap size check mistake.
Thanks, pulled.
BR,
Jani.
>
> Thanks.
> --
> The following changes since commit f0e9943725186ddbdc9718a559c26c5f507262f2:
>
> drm/i915/gvt: Fix workload request allocation before request add (2019-01-09 12:59:09 +0800)
>
> are available in the Git repository at:
>
> https://github.com/intel/gvt-linux.git tags/gvt-fixes-2018-01-17
>
> for you to fetch changes up to 51b00d8509dc69c98740da2ad07308b630d3eb7d:
>
> drm/i915/gvt: Fix mmap range check (2019-01-15 19:04:45 +0800)
>
> ----------------------------------------------------------------
> gvt-fixes-2018-01-17
>
> - Fix one register cmd parser failure (Colin)
> - Fix region cleanup for vGPU destroy (Henry)
> - Fix mmap size check (Zhenyu)
>
> ----------------------------------------------------------------
> Colin Xu (1):
> drm/i915/gvt: Allow F_CMD_ACCESS on mmio 0x21f0
>
> Hang Yuan (1):
> drm/i915/gvt: free VFIO region space in vgpu detach
>
> Zhenyu Wang (1):
> drm/i915/gvt: Fix mmap range check
>
> drivers/gpu/drm/i915/gvt/handlers.c | 1 +
> drivers/gpu/drm/i915/gvt/hypercall.h | 2 +-
> drivers/gpu/drm/i915/gvt/kvmgt.c | 30 ++++++++++++++++++++++++++----
> drivers/gpu/drm/i915/gvt/mpt.h | 2 +-
> 4 files changed, 29 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
prev parent reply other threads:[~2019-01-17 10:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 7:46 [PULL] gvt-fixes for 5.0-rc3 Zhenyu Wang
2019-01-17 10:16 ` Jani Nikula [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=87h8e7fv2p.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).