qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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: Thu, 15 Dec 2011 13:54:03 +0200	[thread overview]
Message-ID: <4EE9DFDB.4050304@redhat.com> (raw)
In-Reply-To: <4EE9CD09.3000901@siemens.com>

On 12/15/2011 12:33 PM, Jan Kiszka wrote:
> >>
> >> Any thoughts on the qemu-kvm merge plan? Sounds painful.
> > 
> > Pain will be where the existing qemu-kvm extensions collide with these
> > refactored upstream devices (backend/frontend split specifically).
> > That's where we have to merge very carefully. Haven't tried this yet,
> > will give it a spin tomorrow or so.
>
> Done yesterday, still seems to work fine. The result can be found at
>
> git://git.kiszka.org/qemu-kvm.git kvm-irqchip-merge
>
> The integration of the upstream irqchip patches was, as expected, not
> that hard. But the merge of my earlier refactorings, the
> backend/frontend split-up caused some efforts.
>
> I'm not sure what to do with that branch. We could either try to merge
> it before pulling in an upstream version that includes the new irqchips.
> But that won't work without manual conflict resolution as well. Or the
> branch can serve as a reference for re-doing a merge later on.

If we merge this before upstream, will the two sides end up equivalent? 
Sounds like it'll be pretty easy to resolve the conflicts if so.

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2011-12-15 11:54 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
2011-12-15 10:33     ` Jan Kiszka
2011-12-15 11:54       ` Avi Kivity [this message]
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=4EE9DFDB.4050304@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).