From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:52575)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1TbTyq-0002hW-Pa
	for qemu-devel@nongnu.org; Thu, 22 Nov 2012 05:26:06 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1TbTyl-000205-02
	for qemu-devel@nongnu.org; Thu, 22 Nov 2012 05:26:00 -0500
Received: from mail-ie0-f173.google.com ([209.85.223.173]:42336)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1TbTyk-000201-Qd
	for qemu-devel@nongnu.org; Thu, 22 Nov 2012 05:25:54 -0500
Received: by mail-ie0-f173.google.com with SMTP id e13so1613267iej.4
	for <qemu-devel@nongnu.org>; Thu, 22 Nov 2012 02:25:54 -0800 (PST)
Sender: Paolo Bonzini <paolo.bonzini@gmail.com>
Message-ID: <50ADFDA8.9010003@redhat.com>
Date: Thu, 22 Nov 2012 11:25:44 +0100
From: Paolo Bonzini <pbonzini@redhat.com>
MIME-Version: 1.0
References: <1353460020.17856.25.camel@pasglop>
In-Reply-To: <1353460020.17856.25.camel@pasglop>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] Interrupt controller updates
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Alexander Graf <agraf@suse.de>, kvm@vger.kernel.org, Peter Maydell <peter.maydell@linaro.org>, Jan Kiszka <jan.kiszka@siemens.com>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, David Gibson <dwg@au1.ibm.com>

Il 21/11/2012 02:07, Benjamin Herrenschmidt ha scritto:
> David (CC) want to make some progress with our in-kernel PIC. From
> memory, one of the outcomes of the BOF was that we need to move the
> existing "enable in-kernel PIC" from generic KVM init to machine init in
> order to be able to add an argument indicating the "model" use by the
> arch/platform since some like ours support several different models and
> since that all needs to be selected before the VCPUs are created.
> 
> Again, from memory, you were volunteered to do the initial x86 change so
> we could piggy back on it :-) Or do I remember wrong ?

Please suggest an API, then we can work out the x86 changes.  I can
volunteer myself, but I wasn't in the BOF so I need something more concrete.

Paolo