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-next
Date: Fri, 1 Feb 2019 09:04:58 -0800 [thread overview]
Message-ID: <20190201170458.GA15784@intel.com> (raw)
In-Reply-To: <20190201061523.GE5588@zhen-hp.sh.intel.com>
On Fri, Feb 01, 2019 at 02:15:23PM +0800, Zhenyu Wang wrote:
>
> Hi,
>
> This should be last gvt-next pull for this round, which adds VFIO edid
> region support in GVT, VM manager can use this to specify custom EDID
> for VM, which can be used for e.g UI resize, etc.
Pulled, thanks
>
> p.s, Next week will be chinese new year, so team will be offline then.
Happy New Year!
>
> Thanks.
> --
> The following changes since commit 2e679d48f38c378650db403b4ba2248adf0691b2:
>
> drm/i915/gvt: switch to kernel types (2019-01-23 13:56:14 +0800)
>
> are available in the Git repository at:
>
> https://github.com/intel/gvt-linux.git tags/gvt-next-2019-02-01
>
> for you to fetch changes up to 39c68e87bc50a71bcfe93582d9b0673ef30db418:
>
> drm/i915/gvt: add VFIO EDID region (2019-01-31 11:41:25 +0800)
>
> ----------------------------------------------------------------
> gvt-next-2019-02-01
>
> - new VFIO EDID region support (Henry)
>
> ----------------------------------------------------------------
> Hang Yuan (3):
> drm/i915/gvt: add functions to get default resolution
> drm/i915/gvt: add hotplug emulation
> drm/i915/gvt: add VFIO EDID region
>
> drivers/gpu/drm/i915/gvt/display.c | 31 ++++++++
> drivers/gpu/drm/i915/gvt/display.h | 37 +++++++--
> drivers/gpu/drm/i915/gvt/gvt.c | 1 +
> drivers/gpu/drm/i915/gvt/gvt.h | 3 +
> drivers/gpu/drm/i915/gvt/hypercall.h | 1 +
> drivers/gpu/drm/i915/gvt/kvmgt.c | 143 +++++++++++++++++++++++++++++++++++
> drivers/gpu/drm/i915/gvt/mpt.h | 17 +++++
> drivers/gpu/drm/i915/gvt/vgpu.c | 6 ++
> 8 files changed, 233 insertions(+), 6 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
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-02-01 17:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 6:15 [PULL] gvt-next Zhenyu Wang
2019-02-01 17:04 ` Rodrigo Vivi [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-13 10:06 Zhenyu Wang
2019-08-13 20:48 ` Rodrigo Vivi
2019-04-09 4:05 Zhenyu Wang
2019-04-16 7:29 ` Joonas Lahtinen
2019-04-16 8:48 ` Zhenyu Wang
2019-04-17 6:40 ` Joonas Lahtinen
2019-01-24 5:40 Zhenyu Wang
2019-01-31 18:02 ` Rodrigo Vivi
2018-06-19 9:00 Zhenyu Wang
2018-06-19 21:46 ` Rodrigo Vivi
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=20190201170458.GA15784@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