All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhiyuan Lv <zhiyuan.lv@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, igvt-g@lists.01.org
Subject: Re: [PATCH 0/7] drm/intel: guest i915 changes for Broadwell to run inside VM with Intel GVT-g
Date: Thu, 20 Aug 2015 16:11:39 +0800	[thread overview]
Message-ID: <20150820081139.GA2853@zlv-hp-dev> (raw)
In-Reply-To: <87y4h6bgsn.fsf@intel.com>

Hi Jani,

On Thu, Aug 20, 2015 at 09:44:08AM +0300, Jani Nikula wrote:
> On Thu, 20 Aug 2015, Zhiyuan Lv <zhiyuan.lv@intel.com> wrote:
> > I915 kernel driver can now work inside a virtual machine on Haswell
> > with Intel GVT-g. In order to do the same thing on Broadwell, there
> > are some extra changes needed. The two main things are to support the
> > more complicated PPGTT page table structure and EXECLIST contexts.
> > GVT-g will perform shadow PPGTT and shadow context, which requires
> > guest driver to explicitly notify host device model the life cycle of
> > PPGTT and EXECLIST contexts.
> >
> > The first and the forth patches added some restrictions to drivers in
> > virtualization scenario to make the shadow work easier. The first
> > patch is based on Mika's earlier one, but we use it for vgpu only.
> > The sixth patch is the implementation of the notification for
> > shadowing.
> 
> Please send your patches with git send-email, or otherwise ensure the
> patches are in-reply-to the cover letter to keep review in one thread.

Thanks for the comments! I just re-sent the patchset, and these ones can be
ignored. Sorry for the inconvenience caused!

Regards,
-Zhiyuan

> 
> BR,
> Jani.
> 
> 
> >
> > Zhiyuan Lv (7):
> >   drm/i915: preallocate pdps for 32 bit vgpu
> >   drm/i915: Enable full ppgtt for vgpu
> >   drm/i915: Always enable execlists on BDW for vgpu
> >   drm/i915: always pin lrc context for vgpu with Intel GVT-g
> >   drm/i915: Update PV INFO page definition for Intel GVT-g
> >   drm/i915: guest i915 notification for Intel-GVTg
> >   drm/i915: Allow Broadwell guest with Intel GVT-g
> >
> >  drivers/gpu/drm/i915/i915_gem_gtt.c | 77 +++++++++++++++++++++++++++++++++++--
> >  drivers/gpu/drm/i915/i915_vgpu.c    |  2 +-
> >  drivers/gpu/drm/i915/i915_vgpu.h    | 34 +++++++++++++++-
> >  drivers/gpu/drm/i915/intel_lrc.c    | 44 ++++++++++++++++++---
> >  4 files changed, 145 insertions(+), 12 deletions(-)
> >
> > -- 
> > 1.9.1
> >
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
> 
> -- 
> Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-08-20  8:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20  3:15 [PATCH 0/7] drm/intel: guest i915 changes for Broadwell to run inside VM with Intel GVT-g Zhiyuan Lv
2015-08-20  6:44 ` Jani Nikula
2015-08-20  8:11   ` Zhiyuan Lv [this message]
2015-08-20  7:45 Zhiyuan Lv

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=20150820081139.GA2853@zlv-hp-dev \
    --to=zhiyuan.lv@intel.com \
    --cc=igvt-g@lists.01.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@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 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.