From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>
Cc: aik@ozlabs.ru, jan.kiszka@siemens.com,
alex.williamson@redhat.com, mst@redhat.com
Subject: [Qemu-devel] [PULL resend] pci,msi,virtio
Date: Sun, 29 Jul 2012 19:41:35 +0300 [thread overview]
Message-ID: <20120729164135.GA14721@redhat.com> (raw)
The following changes since commit 7162ab21fe8e82f924002951cd8e87f69358f8b5:
x86: Fixed incorrect segment base address addition in 64-bits mode (2012-07-29 08:45:57 +0000)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git tags/for_anthony
for you to fetch changes up to 5e59b024351f827f903f98ae522687ea53dc4f23:
Merge branch pci into master (2012-07-29 17:05:35 +0300)
----------------------------------------------------------------
pci,msi,virtio
This pull includes preparation patches mostly by Jan and Alex
that should help merge device assignment down the road.
And there's a new API needed for emulating POWER firmware.
So no new functionality and some unused APIs but it looks like
merging will help people make progress.
This is the same as my previous pull request but I merged
in upstream master and resolved the resulting breakage.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
----------------------------------------------------------------
Alex Williamson (11):
msix: fix PCIDevice naming inconsistency
msix: Add simple BAR allocation MSIX setup functions
ivshmem: Convert to msix_init_exclusive_bar() interface
virtio: Convert to msix_init_exclusive_bar() interface
msix: Move msix_mmio_read
msix: Note endian TODO item
msix: Split PBA into it's own MemoryRegion
msix: Allow full specification of MSIX layout
msix: Switch msix_uninit to return void
pci: convert PCIUnregisterFunc to void
pci: Unregister BARs before device exit
Alexey Kardashevskiy (1):
msi/msix: added API to set MSI message address and data
Jan Kiszka (2):
msix: drop unused msix_bar_size, require valid bar_size
pci: Add INTx routing notifier
Michael S. Tsirkin (2):
pci: Add pci_device_route_intx_to_irq
Merge branch pci into master
hw/ac97.c | 3 +-
hw/e1000.c | 3 +-
hw/eepro100.c | 3 +-
hw/es1370.c | 3 +-
hw/esp.c | 4 +-
hw/ide/cmd646.c | 4 +-
hw/ide/ich.c | 4 +-
hw/ide/piix.c | 4 +-
hw/ide/via.c | 4 +-
hw/intel-hda.c | 3 +-
hw/ioh3420.c | 8 +-
hw/ivshmem.c | 14 +--
hw/lsi53c895a.c | 4 +-
hw/msi.c | 17 +++
hw/msi.h | 1 +
hw/msix.c | 290 ++++++++++++++++++++++++++----------------------
hw/msix.h | 19 ++--
hw/ne2000.c | 3 +-
hw/pci.c | 54 ++++++++-
hw/pci.h | 35 ++++--
hw/pci_bridge.c | 3 +-
hw/pci_bridge.h | 2 +-
hw/pci_bridge_dev.c | 13 +--
hw/pci_internals.h | 1 +
hw/pcnet-pci.c | 3 +-
hw/piix_pci.c | 20 ++++
hw/rtl8139.c | 3 +-
hw/usb/hcd-uhci.c | 3 +-
hw/virtio-pci.c | 36 +++---
hw/virtio-pci.h | 1 -
hw/wdt_i6300esb.c | 4 +-
hw/xio3130_downstream.c | 8 +-
hw/xio3130_upstream.c | 8 +-
33 files changed, 337 insertions(+), 248 deletions(-)
reply other threads:[~2012-07-29 16:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120729164135.GA14721@redhat.com \
--to=mst@redhat.com \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=jan.kiszka@siemens.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).