From: Gerd Hoffmann <kraxel@redhat.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Dave Airlie <airlied@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 1/8] virtio-gpu/2d: add hardware spec include file
Date: Mon, 06 Oct 2014 11:20:31 +0200 [thread overview]
Message-ID: <1412587231.5003.16.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <CAPM=9tyGp-gYHoSCkgPW4zP2NWUyO1kNkaP_YDjjXPBwoV0OyA@mail.gmail.com>
Hi,
> >> >> + VIRTIO_GPU_FORMAT_B5G5R5A1_UNORM = 5,
> >> >> + VIRTIO_GPU_FORMAT_B5G6R5_UNORM = 7,
> >> >
> > Ok. But for 2D we can just not support it, right?
>
> We can, I expect some pushback at some point, people still want to
> test with 16bpp for other areas, and it would be nice to know they
> can. But I don't really care about it personally. I just though we
> should provide at least a basic number of working bpps (8,16,32).
Lets try to get away with 32bpp only in 2d mode then.
bochsdrm likewise supports 32bpp only and I yet have to see a request
for 16bpp or even 8bpp support.
> I think we should probably move a few more formats from the 3D side
> into the 2D side, so we can have the guests just pick the LE format
> it requires
>
> http://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/include/pipe/p_format.h#n354
>
> is what gallium currently does, and we could just provide XRGB, XBGR
> formats in both endianness
> and have the guest pick the one it wants to use.
PIPE_FORMAT_R8G8B8A8_UNORM = 67,
PIPE_FORMAT_X8B8G8R8_UNORM = 68,
PIPE_FORMAT_A8B8G8R8_UNORM = 121,
PIPE_FORMAT_R8G8B8X8_UNORM = 134,
With the last two ones being in a /* TODO: re-order these */ block.
How stable are these numbers?
> The 2D pixman code would need updating to provide 2D support for these
> formats as well.
Yep. Mapping the 32bpp formats to pixmap formats is easy.
> I suspect I could add an endian cap for the 3D bits that I could pass
> through from guest to host.
I was thinking about using virtio feature bit. Advantage is that the
guest will tell the host which features it'll use.
Initially this doesn't matter much as the host will support only one
endianness anyway.
But in case we get the byteswapping work reasonable well some day and
the host supports both be and le virgl we'll know that way which
endianness the guest is using.
> How do you test guests with big endian? Isn't it really slow?
emulated pseries machine with fedora ppc64. Yes, it is slow. Building
a kernel with virtio-gpu driver takes a day or so.
cheers,
Gerd
next prev parent reply other threads:[~2014-10-06 9:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 13:27 [Qemu-devel] [PATCH 0/8] add virtio-gpu Gerd Hoffmann
2014-09-23 13:28 ` [Qemu-devel] [PATCH 1/8] virtio-gpu/2d: add hardware spec include file Gerd Hoffmann
2014-09-25 15:02 ` Gerd Hoffmann
2014-09-30 0:27 ` Dave Airlie
2014-09-30 7:54 ` Gerd Hoffmann
2014-09-30 7:55 ` Gerd Hoffmann
2014-10-03 4:38 ` Dave Airlie
2014-10-06 9:20 ` Gerd Hoffmann [this message]
2014-10-16 3:53 ` Dave Airlie
2014-10-16 12:18 ` Gerd Hoffmann
2014-10-15 10:05 ` Gerd Hoffmann
2014-10-16 3:55 ` Dave Airlie
2014-09-23 13:28 ` [Qemu-devel] [PATCH 2/8] virtio-gpu/2d: add virtio gpu core code Gerd Hoffmann
2014-09-23 13:28 ` [Qemu-devel] [PATCH 3/8] virtio-gpu-pci: add virtio pci support Gerd Hoffmann
2014-09-23 13:28 ` [Qemu-devel] [PATCH 4/8] virtio-vga: add virtio gpu device with vga compatibility Gerd Hoffmann
2014-09-23 13:28 ` [Qemu-devel] [PATCH 5/8] virtio-vga: add '-vga virtio' support Gerd Hoffmann
2014-09-23 13:28 ` [Qemu-devel] [PATCH 6/8] virtio-vga: add vgabios configuration Gerd Hoffmann
2014-09-23 13:28 ` [Qemu-devel] [PATCH 7/8] virtio-vga: add vgabios binary Gerd Hoffmann
2014-09-23 13:28 ` [Qemu-devel] [PATCH 8/8] virtio-gpu: add to display-vga test Gerd Hoffmann
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=1412587231.5003.16.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=qemu-devel@nongnu.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).