From: Jamie Lokier <jamie@shareable.org>
To: Glauber Costa <glommer@redhat.com>
Cc: Avi Kivity <avi@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Re: [PATCH v2 4/9] provide in-kernel apic
Date: Fri, 9 Oct 2009 17:48:31 +0100 [thread overview]
Message-ID: <20091009164831.GB7393@shareable.org> (raw)
In-Reply-To: <20091009143031.GU8092@mothafucka.localdomain>
Glauber Costa wrote:
> On Fri, Oct 09, 2009 at 11:06:41AM +0100, Jamie Lokier wrote:
> > Glauber Costa wrote:
> > > > It ensures the two models are compatible. Since they're the same device
> > > > from the point of view of the guest, there's no reason for them to have
> > > > different representations or to be incompatible.
> > >
> > > live migration between something that has in-kernel irqchip and
> > > something that has not is likely to be a completely untested
> > > thing. And this is the only reason we might think of it as the same
> > > device. I don't see any value in supporting this combination
> >
> > Not just live migration. ACPI sleep + savevm + loadvm + ACPI resume,
> > for example.
> Yes, but in this case too, I'd expect the irqchipness of qemu not to change.
If I've just been sent an image produced by someone running KVM, and
my machine is not KVM-capable, or I cannot upgrade the KVM kernel
module because it's in use by other VMs (had this problem a few
times), there's no choice but to change the irqchipness.
-- Jamie
next prev parent reply other threads:[~2009-10-09 16:49 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1254953315-5761-1-git-send-email-glommer@redhat.com>
[not found] ` <1254953315-5761-2-git-send-email-glommer@redhat.com>
[not found] ` <1254953315-5761-3-git-send-email-glommer@redhat.com>
[not found] ` <1254953315-5761-4-git-send-email-glommer@redhat.com>
2009-10-08 13:49 ` [PATCH v2 3/9] provide in-kernel ioapic Anthony Liguori
2009-10-08 13:54 ` Avi Kivity
2009-10-08 15:53 ` Jan Kiszka
2009-10-08 16:07 ` [Qemu-devel] " Jamie Lokier
2009-10-08 16:12 ` Anthony Liguori
2009-10-08 16:17 ` Avi Kivity
2009-10-08 16:22 ` Gleb Natapov
2009-10-08 16:29 ` Avi Kivity
2009-10-08 16:34 ` Gleb Natapov
2009-10-08 16:42 ` Avi Kivity
2009-10-08 17:11 ` Gleb Natapov
2009-10-09 10:02 ` Jamie Lokier
2009-10-09 12:02 ` [Qemu-devel] " Gleb Natapov
2009-10-09 14:32 ` Glauber Costa
2009-10-09 16:49 ` [Qemu-devel] " Jamie Lokier
2009-10-09 19:55 ` Juan Quintela
2009-10-09 21:34 ` Glauber Costa
2009-10-12 13:20 ` Anthony Liguori
2009-10-12 14:18 ` Jamie Lokier
2009-10-12 14:49 ` Anthony Liguori
[not found] ` <1254953315-5761-5-git-send-email-glommer@redhat.com>
2009-10-08 13:55 ` [PATCH v2 4/9] provide in-kernel apic Anthony Liguori
2009-10-08 14:09 ` Avi Kivity
2009-10-08 14:22 ` [Qemu-devel] " Glauber Costa
2009-10-09 10:06 ` Jamie Lokier
2009-10-09 14:30 ` Glauber Costa
2009-10-09 16:48 ` Jamie Lokier [this message]
2009-10-09 18:06 ` Glauber Costa
2009-10-09 19:49 ` [Qemu-devel] " Anthony Liguori
2009-10-11 9:10 ` Avi Kivity
2009-10-12 13:41 ` [Qemu-devel] " Anthony Liguori
2009-10-08 14:26 ` Anthony Liguori
2009-10-08 14:31 ` Avi Kivity
2009-10-08 14:39 ` Anthony Liguori
2009-10-08 14:46 ` Glauber Costa
2009-10-08 14:44 ` Glauber Costa
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=20091009164831.GB7393@shareable.org \
--to=jamie@shareable.org \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=glommer@redhat.com \
--cc=kvm@vger.kernel.org \
--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).