From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: virtualization@lists.linux-foundation.org,
linux-s390@vger.kernel.org, KVM list <kvm@vger.kernel.org>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Carsten Otte <carsteno@de.ibm.com>,
Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH 2/3] S390: Add virtio hotplug add support
Date: Sun, 12 Sep 2010 11:00:43 +0200 [thread overview]
Message-ID: <4C8C96BB.2010804@redhat.com> (raw)
In-Reply-To: <72A751CE-3F46-4D98-9FAF-BA1C1A95B6EE@suse.de>
On 09/12/2010 02:42 AM, Alexander Graf wrote:
> On 24.08.2010, at 15:48, Alexander Graf wrote:
>
>> The one big missing feature in s390-virtio was hotplugging. This is no more.
>> This patch implements hotplug add support, so you can on the fly add new devices
>> in the guest.
>>
>> Keep in mind that this needs a patch for qemu to actually leverage the
>> functionality.
>>
>> Signed-off-by: Alexander Graf<agraf@suse.de>
> ping (on the patch set)?
>
Actually Marcelo applied it. But the natural place for it is Rusty's
virtio tree. Rusty, if you want to take it, let me know and I'll drop
it from kvm.git.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-09-12 9:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 13:48 [PATCH 1/3] S390: take a full byte as ext_param indicator Alexander Graf
2010-08-24 13:48 ` [PATCH 2/3] S390: Add virtio hotplug add support Alexander Graf
2010-08-25 8:16 ` Heiko Carstens
2010-08-25 8:20 ` Alexander Graf
2010-08-25 8:35 ` Heiko Carstens
2010-08-25 8:34 ` Alexander Graf
2010-08-25 8:48 ` Heiko Carstens
2010-08-25 8:52 ` Alexander Graf
2010-09-12 0:42 ` Alexander Graf
2010-09-12 9:00 ` Avi Kivity [this message]
2010-09-13 3:35 ` Rusty Russell
2010-09-13 7:41 ` Martin Schwidefsky
2010-09-13 9:41 ` Avi Kivity
2010-08-24 13:48 ` [PATCH 3/3] S390: Export kvm_virtio.h Alexander Graf
2010-08-25 21:20 ` [PATCH 1/3] S390: take a full byte as ext_param indicator Marcelo Tosatti
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=4C8C96BB.2010804@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=carsteno@de.ibm.com \
--cc=ehrhardt@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.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).