Re: [Qemu-devel] Interrupt controller updates

2012-11-22 Thread Peter Maydell
On 22 November 2012 21:00, Benjamin Herrenschmidt wrote: > Oh it's simple enough initially, just move the ioctl call from generic > kvm init to machine init. The problem is then to add an argument, since > that essentially means changing the ioctl number, but we need that for > all archs where the

Re: [Qemu-devel] Interrupt controller updates

2012-11-22 Thread Benjamin Herrenschmidt
On Thu, 2012-11-22 at 11:25 +0100, Paolo Bonzini wrote: > > 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

Re: [Qemu-devel] Interrupt controller updates

2012-11-22 Thread Paolo Bonzini
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

Re: [Qemu-devel] Interrupt controller updates

2012-11-21 Thread Jan Kiszka
On 2012-11-21 02:07, Benjamin Herrenschmidt wrote: > Hi Jan ! > > 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 t

[Qemu-devel] Interrupt controller updates

2012-11-20 Thread Benjamin Herrenschmidt
Hi Jan ! 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/platfo