From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Blue Swirl <blauwirbel@gmail.com>
Subject: Re: [Qemu-devel] [PATCH v4 00/15] uq/master: Introduce basic irqchip support
Date: Mon, 12 Dec 2011 19:59:18 +0200 [thread overview]
Message-ID: <4EE640F6.9010809@redhat.com> (raw)
In-Reply-To: <4EE63D13.9070807@siemens.com>
On 12/12/2011 07:42 PM, Jan Kiszka wrote:
> > It's a little late for this, but refactoring qemu-kvm in-tree and then
> > splitting it into patches would have been easier. Let's try it this way
> > for the next batch.
>
> I thought about this, but it definitely takes a clean, qemu-kvm free
> base as start. The point is to design something free of all the legacy,
> only looking at the other code base to extract the logic.
If qemu-kvm was merged into qemu as is, then I'm sure you'd be able to
refactor it into good shape (though there might be a little less
motivation).
> Moreover, there was and still is quite some upstream cleanup necessary,
> and that never goes well with the delta of qemu-kvm.
That's a good point.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-12-12 17:59 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 11:52 [Qemu-devel] [PATCH v4 00/15] uq/master: Introduce basic irqchip support Jan Kiszka
2011-12-08 11:52 ` [Qemu-devel] [PATCH v4 01/15] msi: Generalize msix_supported to msi_supported Jan Kiszka
2011-12-08 11:52 ` [Qemu-devel] [PATCH v4 02/15] kvm: Move kvmclock into hw/kvm folder Jan Kiszka
2011-12-08 11:52 ` [Qemu-devel] [PATCH v4 03/15] apic: Stop timer on reset Jan Kiszka
2011-12-08 11:52 ` [Qemu-devel] [PATCH v4 04/15] apic: Inject external NMI events via LINT1 Jan Kiszka
2011-12-08 11:52 ` [Qemu-devel] [PATCH v4 05/15] apic: Introduce backend/frontend infrastructure for KVM reuse Jan Kiszka
2011-12-08 11:52 ` [Qemu-devel] [PATCH v4 06/15] apic: Open-code timer save/restore Jan Kiszka
2011-12-08 11:52 ` [Qemu-devel] [PATCH v4 07/15] i8259: Introduce backend/frontend infrastructure for KVM reuse Jan Kiszka
2011-12-08 11:52 ` [Qemu-devel] [PATCH v4 08/15] ioapic: " Jan Kiszka
2011-12-08 11:52 ` [Qemu-devel] [PATCH v4 09/15] memory: Introduce memory_region_init_reservation Jan Kiszka
2011-12-08 11:52 ` [Qemu-devel] [PATCH v4 10/15] kvm: Introduce core services for in-kernel irqchip support Jan Kiszka
2011-12-08 11:52 ` [Qemu-devel] [PATCH v4 11/15] kvm: x86: Establish IRQ0 override control Jan Kiszka
2011-12-08 11:52 ` [Qemu-devel] [PATCH v4 12/15] kvm: x86: Add user space part for in-kernel APIC Jan Kiszka
2011-12-08 21:16 ` Blue Swirl
2011-12-09 7:45 ` Jan Kiszka
2011-12-09 7:52 ` Jan Kiszka
2011-12-10 15:40 ` Blue Swirl
2011-12-10 15:58 ` Jan Kiszka
2011-12-10 16:11 ` Blue Swirl
2011-12-08 11:52 ` [Qemu-devel] [PATCH v4 13/15] kvm: x86: Add user space part for in-kernel i8259 Jan Kiszka
2011-12-08 11:52 ` [Qemu-devel] [PATCH v4 14/15] kvm: x86: Add user space part for in-kernel IOAPIC Jan Kiszka
2011-12-08 11:52 ` [Qemu-devel] [PATCH v4 15/15] kvm: Arm in-kernel irqchip support Jan Kiszka
2011-12-08 21:25 ` [Qemu-devel] [PATCH v4 00/15] uq/master: Introduce basic " Blue Swirl
2011-12-09 7:40 ` Jan Kiszka
2011-12-12 16:37 ` Marcelo Tosatti
2011-12-12 16:51 ` Jan Kiszka
2011-12-12 17:37 ` Avi Kivity
2011-12-12 17:42 ` Jan Kiszka
2011-12-12 17:59 ` Avi Kivity [this message]
2011-12-15 10:33 ` Jan Kiszka
2011-12-15 11:54 ` Avi Kivity
2011-12-15 11:59 ` Jan Kiszka
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=4EE640F6.9010809@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=blauwirbel@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=laijs@cn.fujitsu.com \
--cc=mst@redhat.com \
--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).