Re: [Qemu-devel] [RFC] Next gen kvm api

2012-02-07 Thread Avi Kivity
On 02/07/2012 03:08 AM, Alexander Graf wrote: I don't like the idea too much. On s390 and ppc we can set other vcpu's interrupt status. How would that work in this model? It would be a "vm-wide syscall". You can also do that on x86 (through KVM_IRQ_LINE). I really do like the ioctl model

Re: [Qemu-devel] [RFC] Next gen kvm api

2012-02-07 Thread Alexander Graf
On 07.02.2012, at 13:24, Avi Kivity wrote: > On 02/07/2012 03:08 AM, Alexander Graf wrote: >> I don't like the idea too much. On s390 and ppc we can set other vcpu's >> interrupt status. How would that work in this model? > > It would be a "vm-wide syscall". You can also do that on x86 (throug

Re: [Qemu-devel] [RFC] Next gen kvm api

2012-02-07 Thread Avi Kivity
On 02/07/2012 02:51 PM, Alexander Graf wrote: On 07.02.2012, at 13:24, Avi Kivity wrote: > On 02/07/2012 03:08 AM, Alexander Graf wrote: >> I don't like the idea too much. On s390 and ppc we can set other vcpu's interrupt status. How would that work in this model? > > It would be a "vm-wide

Re: [Qemu-devel] [RFC] Next gen kvm api

2012-02-07 Thread Alexander Graf
On 07.02.2012, at 14:16, Avi Kivity wrote: > On 02/07/2012 02:51 PM, Alexander Graf wrote: >> On 07.02.2012, at 13:24, Avi Kivity wrote: >> >> > On 02/07/2012 03:08 AM, Alexander Graf wrote: >> >> I don't like the idea too much. On s390 and ppc we can set other vcpu's >> >> interrupt status.

Re: [Qemu-devel] [RFC] Next gen kvm api

2012-02-07 Thread Avi Kivity
On 02/07/2012 03:40 PM, Alexander Graf wrote: >> >> Not sure we'll ever get there. For PPC, it will probably take another 1-2 years until we get the 32-bit targets stabilized. By then we will have new 64-bit support though. And then the next gen will come out giving us even more new constrain

Re: [Qemu-devel] [RFC] Next gen kvm api

2012-02-07 Thread Alexander Graf
On 07.02.2012, at 15:21, Avi Kivity wrote: > On 02/07/2012 03:40 PM, Alexander Graf wrote: >> >> >> >> Not sure we'll ever get there. For PPC, it will probably take another >> >> 1-2 years until we get the 32-bit targets stabilized. By then we will >> >> have new 64-bit support though. And the

Re: [Qemu-devel] [RFC] Next gen kvm api

2012-02-07 Thread Anthony Liguori
On 02/07/2012 07:40 AM, Alexander Graf wrote: Why? For the HPET timer register for example, we could have a simple MMIO hook that says on_read: return read_current_time() - shared_page.offset; on_write: handle_in_user_space(); For IDE, it would be as simple as register_pio

Re: [Qemu-devel] [RFC] Next gen kvm api

2012-02-07 Thread Alexander Graf
On 07.02.2012, at 16:23, Anthony Liguori wrote: > On 02/07/2012 07:40 AM, Alexander Graf wrote: >> >> Why? For the HPET timer register for example, we could have a simple MMIO >> hook that says >> >> on_read: >> return read_current_time() - shared_page.offset; >> on_write: >> handl