From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 0/2] PCI learns about VGA
Date: Mon, 4 Mar 2013 11:15:29 +0200 [thread overview]
Message-ID: <20130304091529.GA30156@redhat.com> (raw)
In-Reply-To: <20130303171901.15425.61733.stgit@bling.home>
On Sun, Mar 03, 2013 at 10:21:20AM -0700, Alex Williamson wrote:
> Bridges aren't the only thing that needs to know about VGA, any class
> VGA device can register for VGA. This adds infrastructure to PCI to
> allow devices to register VGA regions and incorporates the previous
> PCI bridge only patch to also make use of this. vfio-pci will also
> use the pci_register_vga() interface when attaching VGA devices.
>
> v4: Add common pci_vga_[un]register helpers and convert pci_bridge
> v3: pci_bridge only: add comments and enable bits for snooping & alias
> v2: pci_bridge only: BRIDGE_CONTROL is 2 bytes
Thanks, applied.
> ---
>
> Alex Williamson (2):
> pci: Add PCI VGA helpers
> pci: Teach PCI Bridges about VGA routing
>
>
> hw/pci/pci.c | 65 +++++++++++++++++++++++++++++++++++++++++++++++++++
> hw/pci/pci.h | 21 ++++++++++++++++
> hw/pci/pci_bridge.c | 45 ++++++++++++++++++++++++++++++++++-
> hw/pci/pci_bus.h | 7 +++++
> hw/pci/pcie_port.c | 2 ++
> 5 files changed, 138 insertions(+), 2 deletions(-)
prev parent reply other threads:[~2013-03-04 9:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 17:21 [Qemu-devel] [PATCH v4 0/2] PCI learns about VGA Alex Williamson
2013-03-03 17:21 ` [Qemu-devel] [PATCH v4 1/2] pci: Add PCI VGA helpers Alex Williamson
2013-03-03 17:21 ` [Qemu-devel] [PATCH v4 2/2] pci: Teach PCI Bridges about VGA routing Alex Williamson
2013-03-04 1:39 ` Peter Maydell
2013-03-04 1:52 ` Alex Williamson
2013-03-04 9:09 ` Michael S. Tsirkin
2013-03-04 9:15 ` Michael S. Tsirkin [this message]
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=20130304091529.GA30156@redhat.com \
--to=mst@redhat.com \
--cc=alex.williamson@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).