From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>
Cc: mst@redhat.com, jan.kiszka@siemens.com, jbaron@redhat.com,
yamahata@valinux.co.jp, alex.williamson@redhat.com,
afaerber@suse.de
Subject: [Qemu-devel] [PULL] virtio,pci infrastructure
Date: Mon, 22 Oct 2012 23:51:29 +0200 [thread overview]
Message-ID: <20121022215129.GA420@redhat.com> (raw)
The following changes since commit f354b1a1ee7a1c72d51b42808724a2b10eec315f:
fix CONFIG_QEMU_HELPERDIR generation again (2012-10-22 00:33:56 +0200)
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 ddd0b1dad684f8274c47092c745362dac369c6de:
virtio-net: enable mrg buf header in tap on linux (2012-10-22 21:59:51 +0200)
----------------------------------------------------------------
virtio,pci infrastructure
This includes infrastructure patches that don't do much by themselves
but should help vfio and q35 make progress.
Also included is rework of virtio-net to use iovec APIs
for vector access - helpful to make it more secure
and in preparation for a new feature that will allow
arbitrary s/g layout for guests.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
----------------------------------------------------------------
Alex Williamson (5):
pci: Helper function for testing if an INTx route changed
pci-assign: Use pci_intx_route_changed()
msi: Add msi_get_message()
pci-assign: Use msi_get_message()
pci: Return PCI_INTX_DISABLED when no bus INTx routing support
Isaku Yamahata (4):
pci: pci capability must be in PCI space
pci_ids: add intel 82801BA pci-to-pci bridge id
pci: introduce pci_swizzle_map_irq_fn() for standardized interrupt pin swizzle
pc/piix_pci: factor out smram/pam logic
Jan Kiszka (1):
pci: Add class 0xc05 as 'SMBus'
Jason Baron (2):
pcie: pass pcie window size to pcie_host_mmcfg_update()
pcie: Convert PCIExpressHost to use the QOM.
Michael S. Tsirkin (12):
pci: make each capability DWORD aligned
virtio-net: track host/guest header length
iov: add iov_cpy
virtio-net: avoid sg copy
virtio-net: use safe iov operations for rx
virtio-net: refactor receive_hdr
virtio-net: first s/g is always at start of buf
virtio-net: switch tx to safe iov functions
virtio-net: simplify rx code
virtio-net: minor code simplification
virtio-net: test peer header support at init time
virtio-net: enable mrg buf header in tap on linux
hw/i386/Makefile.objs | 1 +
hw/kvm/pci-assign.c | 8 +--
hw/msi.c | 45 ++++++++-----
hw/msi.h | 1 +
hw/pam.c | 120 ++++++++++++++++++++++++++++++++++
hw/pam.h | 98 ++++++++++++++++++++++++++++
hw/pci.c | 42 ++++++++++--
hw/pci.h | 3 +
hw/pci_ids.h | 2 +
hw/pcie_host.c | 35 +++++++---
hw/pcie_host.h | 12 +++-
hw/piix_pci.c | 65 +++----------------
hw/vhost_net.c | 13 ----
hw/virtio-net.c | 176 ++++++++++++++++++++++++++++----------------------
iov.c | 23 +++++++
iov.h | 9 +++
16 files changed, 466 insertions(+), 187 deletions(-)
create mode 100644 hw/pam.c
create mode 100644 hw/pam.h
reply other threads:[~2012-10-22 21:49 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=20121022215129.GA420@redhat.com \
--to=mst@redhat.com \
--cc=afaerber@suse.de \
--cc=alex.williamson@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=jan.kiszka@siemens.com \
--cc=jbaron@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yamahata@valinux.co.jp \
/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).