qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>
Cc: stefano.stabellini@eu.citrix.com, rusty@rustcorp.com.au,
	akong@redhat.com, dkoch@verizon.com, mst@redhat.com
Subject: [Qemu-devel] [PULL 0/5] pci,net,pc enhancements
Date: Wed, 17 Jul 2013 12:47:57 +0300	[thread overview]
Message-ID: <1374054430-21966-1-git-send-email-mst@redhat.com> (raw)

From: Michael S. Tsirkin <mst@redhat.com>

The following changes since commit 7588e2b0559ae72d3c2952c7807fc05c03099970:

  pci: Fold host_buses list into PCIHostState functionality (2013-07-07 23:10:57 +0300)

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 d26d9e14c15837eba2b7447e8d15230bab8e0940:

  pc: don't access fw cfg if NULL (2013-07-15 21:26:32 +0300)

----------------------------------------------------------------
pci,net,pc enhancements

This includes some fixes and enhancements that accumulated in my tree:
pci fixes by dkoch, virtio-net enhancements by akong and mst,
and a fix for xen pc by mst.

Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

----------------------------------------------------------------
Amos Kong (1):
      net: add support of mac-programming over macvtap in QEMU side

Don Koch (2):
      pci-bridge: update mappings for migration/restore
      pci: fix BRDIGE typo

Michael S. Tsirkin (2):
      virtio-net: add feature bit for any header s/g
      pc: don't access fw cfg if NULL

 QMP/qmp-events.txt             |  17 ++++++
 hw/i386/pc.c                   |   2 +-
 hw/net/virtio-net.c            | 133 +++++++++++++++++++++++++++++++++++++++--
 hw/pci-bridge/i82801b11.c      |   2 +-
 hw/pci/pci.c                   |   5 ++
 hw/pci/pci_bridge.c            |   2 +-
 include/hw/i386/pc.h           |   4 ++
 include/hw/pci/pci_bridge.h    |   1 +
 include/hw/pci/pci_ids.h       |   2 +-
 include/hw/virtio/virtio-net.h |   1 +
 include/hw/virtio/virtio.h     |   2 +
 include/monitor/monitor.h      |   1 +
 include/net/net.h              |   3 +
 monitor.c                      |   1 +
 net/net.c                      |  48 +++++++++++++++
 qapi-schema.json               |  76 +++++++++++++++++++++++
 qmp-commands.hx                |  63 +++++++++++++++++++
 17 files changed, 353 insertions(+), 10 deletions(-)

             reply	other threads:[~2013-07-17  9:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-17  9:47 Michael S. Tsirkin [this message]
2013-07-17  9:48 ` [Qemu-devel] [PULL 1/5] pci-bridge: update mappings for migration/restore Michael S. Tsirkin
2013-07-17  9:48 ` [Qemu-devel] [PULL 2/5] pci: fix BRDIGE typo Michael S. Tsirkin
2013-07-17  9:48 ` [Qemu-devel] [PULL 3/5] net: add support of mac-programming over macvtap in QEMU side Michael S. Tsirkin
2013-07-17  9:48 ` [Qemu-devel] [PULL 4/5] virtio-net: add feature bit for any header s/g Michael S. Tsirkin
2013-07-17  9:48 ` [Qemu-devel] [PULL 5/5] pc: don't access fw cfg if NULL Michael S. Tsirkin

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=1374054430-21966-1-git-send-email-mst@redhat.com \
    --to=mst@redhat.com \
    --cc=akong@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=dkoch@verizon.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rusty@rustcorp.com.au \
    --cc=stefano.stabellini@eu.citrix.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 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).