From: Anthony Liguori <anthony@codemonkey.ws>
To: Jamie Lokier <jamie@shareable.org>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Juan Quintela <quintela@trasno.org>,
Glauber Costa <glommer@redhat.com>,
kvm-devel <kvm@vger.kernel.org>, Avi Kivity <avi@redhat.com>,
Gleb Natapov <gleb@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v2 3/9] provide in-kernel ioapic
Date: Mon, 12 Oct 2009 09:49:54 -0500 [thread overview]
Message-ID: <4AD34212.9060805@codemonkey.ws> (raw)
In-Reply-To: <20091012141825.GC13560@shareable.org>
Jamie Lokier wrote:
> Anthony Liguori wrote:
>
>> We already have the single device model implementation and the
>> limitations are well known. The best way to move forward is for someone
>> to send out patches implementing separate device models.
>>
>> At that point, it becomes a discussion of two concrete pieces of code
>> verses hand waving.
>>
>
> Out of curiosity now, what _are_ the behavioural differences between
> the in-kernel irqchip and the qemu one?
>
> Are the differences significant to guests, such that it might be
> necessary to disable the in-kernel irqchip for some guests, or
> conversely, necessary to use KVM for some guests?
>
No, the behavior differences are not terribly significant for the apic.
Disabling it is really most useful for debugging purposes.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-10-12 14:51 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 [this message]
[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 ` [Qemu-devel] " Jamie Lokier
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=4AD34212.9060805@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=glommer@redhat.com \
--cc=jamie@shareable.org \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@trasno.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.