public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Zhiyuan Lv <zhiyuan.lv@intel.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: daniel.vetter@ffwll.ch, intel-gfx@lists.freedesktop.org,
	igvt-g@lists.01.org, david.j.cowperthwaite@intel.com
Subject: Re: Ask for comments of getting guest framebuffer in igvt-g
Date: Fri, 4 Mar 2016 23:38:25 +0800	[thread overview]
Message-ID: <20160304153824.GA11819@zlv-hp-dev> (raw)
In-Reply-To: <1457100027.8300.5.camel@linux.intel.com>

Hi Joonas,

On Fri, Mar 04, 2016 at 04:00:27PM +0200, Joonas Lahtinen wrote:
> Hi,
> 
> On to, 2016-03-03 at 17:50 +0800, Zhiyuan Lv wrote:
> > Dear i915 developers,
> > 
> > Here I have one topic hoping to get your comments and suggestions.
> > Basically it is about graphics virtualization(igvt-g), for the purpose
> > of host system to get virtual machine's framebuffer. We would like to
> > hear your opinions about some design opens. Below is the
> > patch and some more detailed description. We appreciate your time
> > on that, and thanks in advance for any comments!
> > 
> > https://patchwork.freedesktop.org/patch/71852/
> > 
> > When people try igvt-g, one common question we heard is how to get
> > guest VM's framebuffer. It is for various purposes:
> > 
> >  - A compositor in host (it can be QEMU itself or other viewer
> >    applications) can use the contents to render a window in host;
> > 
> >  - Remote protocol can easily handle it to support 3D/Media
> >    accelerated VMs;
> > 
> > The specific requirements include:
> > 
> >  - Be able to map the guest framebuffer so that host CPU can read it;
> >  - Be able to export guest framebuffer through dam_buf;
> >  - Be able to direct render with guest framebuffers;
> > 
> > In order to support that, we introduced a new gem object called
> > gvtbuffer. It is a special object with guest framebuffer's pages as
> > its backing storage. Meanwhile, it could behave normally like other
> > gem objects. It can be mapped, exported and used by EGL APIs.
> > 
> > Although we say guest fb pages for gvtbuffer, the solution itself is
> > safe. Because gvtbuffer gets entries from physical GGTT which cannot
> > be accessed by guest VM directly. igvt-g device model is responsible
> > for filling physical GGTT after translating the iova from guest GGTT
> > table. Even if a malicious guest uses a bad framebuffer, the pages
> > filled in GGTT are always valid. Then when gvtbuffer tries to get some
> > entries, they are always valid address not causing hardware problems.
> > 
> > It is possible, however, that the guest VM performs page flip while
> > gvtbuffer is attached with the framebuffer, and is being used for
> > rendering. That may cause some tearing in theory. But in practice, we
> > did not see that. If that is a concern, we can consider to delay the
> > VBLANK irq injection to guest as a solution.
> > 
> 
> Could you elborate here? I guess the idea is to make the guest think it
> is operating with regular hardware. So I think the owner of a gvtbuffer
> will inject the vblank when it has consumed the current framebuffer
> data, pretty much like with real hardware. Or what else would trigger
> vblank?

The igvt device model is responsible for injecting vblank interrupts to VMs
for i915 running inside. Currently we have a timer for the regular vblank
injection. So if needed, host i915 can notify gvt device model to delay
vblank for a VM, hence delay the flip from VM's point of view. BTW, the idea
of delay is not in current gvt code. We are not sure whether it is a must to
have and whether it is the best way. Just feel that it is doable. Thanks!

Regards,
-Zhiyuan

> 
> Otherwise tearing can not be avoided. Or will the guest be more aware
> of being under graphics virtualization than that?
> 
> Regards, Joonas
> 
> > So in general, do you think it is OK to introduce the gvtbuffer gem
> > object, or there could be better way to handle it in gem framework?
> > 
> > Currently we have a new IOCTL added for the gvtbuffer, and we also
> > added some data structures to describe the framebuffer format for user
> > mode. Do you think that is fine? Thanks again!
> > 
> > Regards,
> > -Zhiyuan
> -- 
> Joonas Lahtinen
> Open Source Technology Center
> Intel Corporation
> _______________________________________________
> 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

  reply	other threads:[~2016-03-04 15:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-03  9:50 Ask for comments of getting guest framebuffer in igvt-g Zhiyuan Lv
2016-03-04 14:00 ` Joonas Lahtinen
2016-03-04 15:38   ` Zhiyuan Lv [this message]
2016-03-07 10:20     ` Joonas Lahtinen
2016-03-08  1:25       ` Zhiyuan Lv
2016-03-08  1:44         ` [iGVT-g] " Tian, Kevin
2016-03-08  8:36           ` Gerd Hoffmann
2016-03-10  5:59             ` Tian, Kevin
2016-03-10 10:00             ` Joonas Lahtinen
2016-03-08  2:44 ` Tian, Kevin
2016-03-08  3:09   ` 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=20160304153824.GA11819@zlv-hp-dev \
    --to=zhiyuan.lv@intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=david.j.cowperthwaite@intel.com \
    --cc=igvt-g@lists.01.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=joonas.lahtinen@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox