From: Jamie Lokier <jamie@shareable.org>
To: Glauber Costa <glommer@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/6] in kernel irqchip support
Date: Tue, 29 Sep 2009 01:39:58 +0100 [thread overview]
Message-ID: <20090929003958.GA5527@shareable.org> (raw)
In-Reply-To: <1254172517-28216-1-git-send-email-glommer@redhat.com>
Glauber Costa wrote:
>I am ready to advocate that it should be the default, whenever
>available. I plan to, however, provide a patch that disables it
>whenever this gets merged.
Is the in-kernel irqchip simply intended to accelerate some part of
the CPU/irq emulation, so that you could enable or disable it at will,
as well as migrating to TCG-using systems and back, with no observable
effect except performance?
-- Jamie
next prev parent reply other threads:[~2009-09-29 0:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 21:15 [Qemu-devel] [PATCH 0/6] in kernel irqchip support Glauber Costa
2009-09-28 21:15 ` [Qemu-devel] [PATCH 1/6] provide in-kernel ioapic Glauber Costa
2009-09-28 21:15 ` [Qemu-devel] [PATCH 2/6] provide in-kernel apic Glauber Costa
2009-09-28 21:15 ` [Qemu-devel] [PATCH 3/6] provide apic_set_irq_delivered Glauber Costa
2009-09-28 21:15 ` [Qemu-devel] [PATCH 4/6] provide in-kernel i8259 chip Glauber Costa
2009-09-28 21:15 ` [Qemu-devel] [PATCH 5/6] initialize " Glauber Costa
2009-09-28 21:15 ` [Qemu-devel] [PATCH 6/6] Initialize in-kernel irqchip Glauber Costa
2009-10-02 20:33 ` [Qemu-devel] " Jan Kiszka
2009-10-02 21:59 ` Jamie Lokier
2009-10-02 22:22 ` Glauber Costa
2009-09-28 22:04 ` [Qemu-devel] Re: [PATCH 4/6] provide in-kernel i8259 chip Juan Quintela
2009-09-28 22:25 ` Glauber Costa
2009-09-28 22:39 ` Juan Quintela
2009-10-02 20:33 ` Jan Kiszka
[not found] ` <m3my4eagcp.fsf@neno.mitica>
2009-09-28 22:24 ` [Qemu-devel] Re: [PATCH 1/6] provide in-kernel ioapic Glauber Costa
2009-09-29 0:39 ` Jamie Lokier [this message]
2009-09-29 1:06 ` [Qemu-devel] [PATCH 0/6] in kernel irqchip support Glauber Costa
2009-09-29 8:15 ` Avi Kivity
2009-09-30 20:01 ` 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=20090929003958.GA5527@shareable.org \
--to=jamie@shareable.org \
--cc=aliguori@us.ibm.com \
--cc=glommer@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).