From: Zhiyuan Lv <zhiyuan.lv@intel.com>
To: "Tian, Kevin" <kevin.tian@intel.com>, Gerd Hoffmann <kraxel@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
"Song, Jike" <jike.song@intel.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
"igvt-g@ml01.01.org" <igvt-g@ml01.01.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"White, Michael L" <michael.l.white@intel.com>,
"Dong, Eddie" <eddie.dong@intel.com>,
"Li, Susie" <susie.li@intel.com>,
"Cowperthwaite, David J" <david.j.cowperthwaite@intel.com>,
"Reddy, Raghuveer" <raghuveer.reddy@intel.com>,
"Zhu, Libo" <libo.zhu@intel.com>,
"Zhou, Chao" <chao.zhou@intel.com>,
"Wang, Hongbo" <hongbo.wang@intel.com>,
qemu-devel <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Intel-gfx] [Announcement] 2015-Q3 release of XenGT - a Mediated Graphics Passthrough Solution from Intel
Date: Fri, 20 Nov 2015 16:46:38 +0800 [thread overview]
Message-ID: <20151120084638.GA13304@zlv-hp-dev> (raw)
In-Reply-To: <AADFC41AFE54684AB9EE6CBC0274A5D15F717B17@SHSMSX101.ccr.corp.intel.com>
On Fri, Nov 20, 2015 at 04:36:15PM +0800, Tian, Kevin wrote:
> > From: Gerd Hoffmann [mailto:kraxel@redhat.com]
> > Sent: Friday, November 20, 2015 4:26 PM
> >
> > Hi,
> >
> > > > iGVT-g_Setup_Guide.txt mentions a "Indirect Display Mode", but doesn't
> > > > explain how the guest framebuffer can be accessed then.
> > >
> > > You can check "fb_decoder.h". One thing to clarify. Its format is
> > > actually based on drm definition, instead of OpenGL. Sorry for
> > > that.
> >
> > drm is fine. That header explains the format, but not how it can be
> > accessed. Is the guest fb exported as dma-buf?
>
> Currently not, but per our previous discussion we should move to use
> dma-buf. We have some demo code in user space. Not sure whether
> they're public now. Jike could you help do a check?
Our current implementation did not use dma-buf yet, still based on DRM_FLINK
interface. We will switch to dma-buf. Thanks!
Regards,
-Zhiyuan
>
> >
> > > > So, for non-opengl rendering qemu needs the guest framebuffer data so it
> > > > can feed it into the vnc server. The vfio framebuffer region is meant
> > > > to support this use case.
> > >
> > > what's the format requirement on that framebuffer? If you are familiar
> > > with Intel Graphics, there's a so-called tiling feature applied on frame
> > > buffer so it can't be used as a raw input to vnc server. w/o opengl you
> > > need do some conversion on CPU first.
> >
> > Yes, that conversion needs to happen, qemu can't deal with tiled
> > graphics. Anything which pixman can handle will work. Prefered would
> > be PIXMAN_x8r8g8b8 (aka DRM_FORMAT_XRGB8888 on little endian host) which
> > is the format used by the vnc server (and other places in qemu)
> > internally.
> >
> > qemu can also use the opengl texture for the guest fb, then fetch the
> > data with glReadPixels(). Which will probably do exactly the same
> > conversion. But it'll add a opengl dependency to the non-opengl
> > rendering path in qemu, would be nice if we can avoid that.
> >
> > While being at it: When importing a dma-buf with a tiled framebuffer
> > into opengl (via eglCreateImageKHR + EGL_LINUX_DMA_BUF_EXT) I suspect we
> > have to pass in the tile size as attribute to make it work. Is that
> > correct?
> >
>
> I'd guess so, but need double confirm later when reaching that level of detail.
> some homework on dma-buf is required first. :-)
>
> Thanks
> Kevin
next prev parent reply other threads:[~2015-11-20 8:55 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 8:31 [Intel-gfx] [Announcement] Updates to XenGT - a Mediated Graphics Passthrough Solution from Intel Jike Song
2014-07-29 10:09 ` [Xen-devel] " Dario Faggioli
2014-07-30 9:39 ` Jike Song
2014-12-04 2:45 ` [Intel-gfx] [Announcement] 2014-Q3 release of " Jike Song
2014-12-04 10:20 ` [Xen-devel] " Fabio Fantoni
2015-01-09 8:51 ` [Intel-gfx] [Announcement] 2015-Q1 " Jike Song
2015-01-12 3:04 ` [Intel-gfx] [Announcement] 2014-Q4 " Jike Song
2015-04-10 13:23 ` [Intel-gfx] [Announcement] 2015-Q1 " Jike Song
2015-07-07 2:49 ` [Intel-gfx] [Announcement] 2015-Q2 " Jike Song
2015-10-27 9:25 ` [Intel-gfx] [Announcement] 2015-Q3 " Jike Song
2015-11-18 18:12 ` Alex Williamson
2015-11-19 4:06 ` Tian, Kevin
2015-11-19 7:22 ` Jike Song
2015-11-19 15:32 ` Stefano Stabellini
2015-11-19 15:49 ` Paolo Bonzini
2015-11-19 16:12 ` Stefano Stabellini
2015-11-19 15:52 ` Alex Williamson
2015-11-20 2:58 ` Jike Song
2015-11-20 4:22 ` Alex Williamson
2015-11-20 5:51 ` Jike Song
2015-11-20 6:01 ` Tian, Kevin
2015-11-20 16:40 ` Alex Williamson
2015-11-23 4:52 ` [Qemu-devel] " Jike Song
2015-11-19 8:40 ` Gerd Hoffmann
2015-11-19 11:09 ` Paolo Bonzini
2015-11-20 2:46 ` Jike Song
2015-11-20 6:12 ` Tian, Kevin
2015-11-20 8:26 ` Gerd Hoffmann
2015-11-20 8:36 ` Tian, Kevin
2015-11-20 8:46 ` Zhiyuan Lv [this message]
2015-12-03 6:57 ` Tian, Kevin
2015-12-04 10:13 ` Gerd Hoffmann
2015-11-19 20:02 ` Alex Williamson
2015-11-20 7:09 ` Tian, Kevin
2015-11-20 17:03 ` Alex Williamson
2015-11-20 8:10 ` Tian, Kevin
2015-11-20 17:25 ` Alex Williamson
2015-11-23 5:05 ` Jike Song
2015-11-24 11:19 ` Daniel Vetter
2015-11-24 11:49 ` Chris Wilson
2015-11-24 12:38 ` Gerd Hoffmann
2015-11-24 13:31 ` Daniel Vetter
2015-11-24 14:12 ` Gerd Hoffmann
2015-11-24 14:19 ` Daniel Vetter
2016-01-27 6:21 ` [Intel-gfx] [Announcement] 2015-Q4 " Jike Song
2016-04-28 5:29 ` [Intel-gfx] [Announcement] 2016-Q1 " Jike Song
2016-07-22 5:42 ` [Intel-gfx] [Announcement] 2016-Q2 " Jike Song
2016-11-06 14:59 ` [Intel-gfx] [Announcement] 2016-Q3 " Jike Song
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=20151120084638.GA13304@zlv-hp-dev \
--to=zhiyuan.lv@intel.com \
--cc=alex.williamson@redhat.com \
--cc=chao.zhou@intel.com \
--cc=david.j.cowperthwaite@intel.com \
--cc=eddie.dong@intel.com \
--cc=hongbo.wang@intel.com \
--cc=igvt-g@ml01.01.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jike.song@intel.com \
--cc=kevin.tian@intel.com \
--cc=kraxel@redhat.com \
--cc=libo.zhu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.l.white@intel.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=raghuveer.reddy@intel.com \
--cc=susie.li@intel.com \
--cc=xen-devel@lists.xen.org \
/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).