From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
KVM list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [PULL] KVM updates
Date: Tue, 11 Sep 2012 11:50:06 +0300 [thread overview]
Message-ID: <504EFB3E.7070508@redhat.com> (raw)
In-Reply-To: <87fw6pbhvu.fsf@codemonkey.ws>
On 09/11/2012 02:03 AM, Anthony Liguori wrote:
> Avi Kivity <avi@redhat.com> writes:
>
>> Please pull from:
>>
>> git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git uq/master
>>
>> to merge some kvm updates, most notably a port of qemu-kvm's pre-vfio device
>> assignment. With this there are no significant changes left between qemu and
>> qemu-kvm (though some work remains).
>
> Pulled. Thanks.
>
> I took a look at the difference, appears to be some deprecated options
> and CPU hotplug. What's the plan there?
#include <jan.h>?
> Is CPU hotplug functional in qemu-kvm?
Last I tested, yes. But it was a long time ago and it isn't part of my
autotest runs.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-09-11 8:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 15:25 [Qemu-devel] [PULL] KVM updates Avi Kivity
2012-09-10 15:32 ` Jan Kiszka
2012-09-10 15:49 ` Marcelo Tosatti
2012-09-10 15:54 ` Avi Kivity
2012-09-10 23:03 ` Anthony Liguori
2012-09-11 8:50 ` Avi Kivity [this message]
2012-09-11 9:30 ` Jan Kiszka
-- strict thread matches above, loose matches on Subject: below --
2012-08-12 12:58 [Qemu-devel] [PULL] kvm updates Avi Kivity
2012-08-13 21:13 ` Anthony Liguori
2012-06-11 13:38 Avi Kivity
2012-06-11 18:28 ` Anthony Liguori
2012-03-01 12:47 Avi Kivity
2012-03-01 23:45 ` Andreas Färber
2012-03-04 10:08 ` Avi Kivity
2012-03-02 13:22 ` 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=504EFB3E.7070508@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--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).