From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>, mst@redhat.com
Subject: [Qemu-devel] [PATCH 0/9] virtio-1.0: cleanups and preparations for virtio-vga
Date: Fri, 10 Apr 2015 14:31:42 +0200 [thread overview]
Message-ID: <1428669111-24225-1-git-send-email-kraxel@redhat.com> (raw)
Hi,
Here is a series of patches for virtio-pci, with some cleanups and
preparations for virtio-vga.
Patches 1-6 clean up the modern (virtio-1.0) memory region
initialization a bit. They are preparations for the other patches,
but IMHO are also a useful cleanup on their own.
Patches 7+8 changes initialization so virtio-vga has a chance to
arrange things as it pleases.
Patches 1-8 should apply fine on top of mst's virtio-1.0 branch, and
I'm looking for reviews of them.
Patch 9 is the showcase for patches 7+8. It has more dependencies
though, if you wanna play with that I'd suggest to fetch
https://www.kraxel.org/cgit/qemu/log/?h=rebase/vga-wip
cheers,
Gerd
Gerd Hoffmann (9):
virtio: add struct VirtIOPCIRegion for virtio-1 regions
virtio: add virtio_pci_modern_regions_init()
virtio: add virtio_pci_modern_region_map()
virtio: move virtio_pci_add_mem_cap call to
virtio_pci_modern_region_map
virtio: move cap type to VirtIOPCIRegion
virtio: drop identical virtio_pci_cap
virtio: move bar assignments to VirtIOPCIProxy
virtio: init from virtio_pci_device_plugged to virtio_pci_realize
virtio-vga: make compatible with stdvga
hw/display/vga-pci.c | 8 +-
hw/display/vga_int.h | 6 ++
hw/display/virtio-vga.c | 20 ++++-
hw/virtio/virtio-pci.c | 228 ++++++++++++++++++++++++------------------------
hw/virtio/virtio-pci.h | 17 +++-
5 files changed, 157 insertions(+), 122 deletions(-)
--
1.8.3.1
next reply other threads:[~2015-04-10 12:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 12:31 Gerd Hoffmann [this message]
2015-04-10 12:31 ` [Qemu-devel] [PATCH 1/9] virtio: add struct VirtIOPCIRegion for virtio-1 regions Gerd Hoffmann
2015-04-10 12:31 ` [Qemu-devel] [PATCH 2/9] virtio: add virtio_pci_modern_regions_init() Gerd Hoffmann
2015-04-10 12:31 ` [Qemu-devel] [PATCH 3/9] virtio: add virtio_pci_modern_region_map() Gerd Hoffmann
2015-04-10 12:31 ` [Qemu-devel] [PATCH 4/9] virtio: move virtio_pci_add_mem_cap call to virtio_pci_modern_region_map Gerd Hoffmann
2015-04-10 12:31 ` [Qemu-devel] [PATCH 5/9] virtio: move cap type to VirtIOPCIRegion Gerd Hoffmann
2015-04-10 12:31 ` [Qemu-devel] [PATCH 6/9] virtio: drop identical virtio_pci_cap Gerd Hoffmann
2015-04-10 12:31 ` [Qemu-devel] [PATCH 7/9] virtio: move bar assignments to VirtIOPCIProxy Gerd Hoffmann
2015-04-10 12:31 ` [Qemu-devel] [PATCH 8/9] virtio: init from virtio_pci_device_plugged to virtio_pci_realize Gerd Hoffmann
2015-04-10 12:31 ` [Qemu-devel] [PATCH 9/9] virtio-vga: make compatible with stdvga Gerd Hoffmann
2015-04-27 9:45 ` [Qemu-devel] [PATCH 0/9] virtio-1.0: cleanups and preparations for virtio-vga Gerd Hoffmann
2015-04-27 10:15 ` Michael S. Tsirkin
2015-04-27 10:23 ` Cornelia Huck
2015-04-27 10:37 ` Michael S. Tsirkin
2015-04-27 10:44 ` 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=1428669111-24225-1-git-send-email-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=mst@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).