All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>
Cc: stefanha@linux.vnet.ibm.com, quintela@redhat.com, mst@redhat.com,
	alex.williamson@redhat.com, kraxel@redhat.com,
	aurelien@aurel32.net
Subject: [Qemu-devel] [PULL] rtl8139, pci, ioeventfd
Date: Wed, 12 Jan 2011 00:42:11 +0200	[thread overview]
Message-ID: <20110111224210.GA17261@redhat.com> (raw)

The following changes since commit 05bf441eb69a813d3893174d54faa6afa8c0d39b:

  cris: Remove unused orig_flags (2011-01-10 23:28:08 +0100)

are available in the git repository at:
  git://git.kernel.org/pub/scm/linux/kernel/git/mst/qemu.git for_anthony

Alex Williamson (2):
      qdev: Track runtime machine modifications
      rtl8139: Use subsection to restrict migration after hotplug

Gerd Hoffmann (4):
      pci: allow devices being tagged as not hotpluggable.
      piix: tag as not hotpluggable.
      vga: tag as not hotplugable.
      qxl: tag as not hotpluggable

Michael S. Tsirkin (3):
      Merge remote branch 'origin/master' into pci
      virtio: move vmstate change tracking to core
      ioeventfd: error handling cleanup

Stefan Hajnoczi (4):
      virtio-pci: Rename bugs field to flags
      kvm: test for ioeventfd support on old kernels
      virtio-pci: Use ioeventfd for virtqueue notify
      docs: Document virtio PCI -device ioeventfd=on|off

 Makefile.objs            |    4 +-
 Makefile.target          |    2 +
 docs/qdev-device-use.txt |    8 ++-
 hmp-commands.hx          |   25 +++++
 hw/acpi_piix4.c          |    2 +
 hw/cirrus_vga.c          |    1 +
 hw/ide/piix.c            |    2 +
 hw/pc_piix.c             |   12 +--
 hw/pci-stub.c            |   50 ++++++++++
 hw/pci.c                 |   92 ++++++++++++++++++--
 hw/pci.h                 |    5 +
 hw/pcie.c                |   11 +--
 hw/pcie.h                |    2 -
 hw/pcie_aer.c            |  223 ++++++++++++++++++++++++++++++++++++++++++++++
 hw/piix4.c               |    1 +
 hw/piix_pci.c            |    2 +
 hw/qdev.c                |   23 ++++-
 hw/qdev.h                |    6 +-
 hw/qxl.c                 |    1 +
 hw/rtl8139.c             |   28 ++++++-
 hw/vga-pci.c             |    1 +
 hw/virtio-net.c          |   28 ++-----
 hw/virtio-pci.c          |  213 ++++++++++++++++++++++++++++++++++++++------
 hw/virtio.c              |   36 +++++++-
 hw/virtio.h              |    4 +
 hw/vmware_vga.c          |    1 +
 hw/xio3130_downstream.c  |    2 +-
 hw/xio3130_upstream.c    |    3 -
 kvm-all.c                |   49 ++++++++++
 kvm-stub.c               |    5 +
 kvm.h                    |    1 +
 qerror.c                 |    4 +
 qerror.h                 |    3 +
 sysemu.h                 |    5 +
 vl.c                     |    4 +-
 35 files changed, 769 insertions(+), 90 deletions(-)
 create mode 100644 hw/pci-stub.c

             reply	other threads:[~2011-01-11 22:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11 22:42 Michael S. Tsirkin [this message]
2011-01-17 16:15 ` [Qemu-devel] [PULL] rtl8139, pci, ioeventfd Anthony Liguori

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=20110111224210.GA17261@redhat.com \
    --to=mst@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=aurelien@aurel32.net \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=stefanha@linux.vnet.ibm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.