qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Cc: kwolf@suse.de, armbru@redhat.com
Subject: [Qemu-devel] [PATCH 0/4] S390 virtio hotplug v2
Date: Tue, 12 Jul 2011 09:21:33 +0200	[thread overview]
Message-ID: <1310455297-27436-1-git-send-email-agraf@suse.de> (raw)

Hey guys,

this patch set adds support for hotplug add on S390. Apparently it's the first
non-x86 platform receiving so much love in Qemu, so I've stumbled over some
very basic #if defined(TARGET_I386) cases that just shouldn't be there.

It's trying to make things as generic as possible. I've talked to Markus about
this vs blockdev and he's fine with pulling in a "dirty" solution in case the
right one takes too long. But we haven't decided on which one is more clean :).

Alex

Alexander Graf (4):
  [S390] Add hotplug support
  Compile device-hotplug on all targets
  Add generic drive hotplugging
  Expose drive_add on all architectures

 Makefile.target      |    5 +++-
 hmp-commands.hx      |    2 -
 hw/device-hotplug.c  |   51 ++++++++++++++++++++++++++++++++++++++++++++++++++
 hw/pci-hotplug.c     |   24 +++-------------------
 hw/s390-virtio-bus.c |   24 ++++++++++++++++++----
 hw/s390-virtio-bus.h |    5 ++++
 sysemu.h             |    6 ++++-
 7 files changed, 88 insertions(+), 29 deletions(-)

             reply	other threads:[~2011-07-13 14:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-12  7:21 Alexander Graf [this message]
2011-07-12  7:21 ` [Qemu-devel] [PATCH 1/4] [S390] Add hotplug support Alexander Graf
2011-07-12  7:21 ` [Qemu-devel] [PATCH 2/4] Compile device-hotplug on all targets Alexander Graf
2011-07-12  7:21 ` [Qemu-devel] [PATCH 3/4] Add generic drive hotplugging Alexander Graf
2011-07-14 12:13   ` Kevin Wolf
2011-07-18  8:18     ` Alexander Graf
2011-07-12  7:21 ` [Qemu-devel] [PATCH 4/4] Expose drive_add on all architectures Alexander Graf

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=1310455297-27436-1-git-send-email-agraf@suse.de \
    --to=agraf@suse.de \
    --cc=armbru@redhat.com \
    --cc=kwolf@suse.de \
    --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).