Re: [PATCH] KVM: x86: Extend KVM_SET_VCPU_EVENTS with selective updates

2009-12-15 Thread Avi Kivity
On 12/06/2009 07:12 PM, Jan Kiszka wrote: Avi Kivity wrote: On 12/06/2009 06:55 PM, Jan Kiszka wrote: User space may not want to overwrite asynchronously changing VCPU event states on write-back. So allow to skip nmi.pending and sipi_vector by setting corresponding bits in the flags

Re: [PATCH] KVM: x86: Extend KVM_SET_VCPU_EVENTS with selective updates

2009-12-15 Thread Jan Kiszka
Avi Kivity wrote: On 12/06/2009 07:12 PM, Jan Kiszka wrote: Avi Kivity wrote: On 12/06/2009 06:55 PM, Jan Kiszka wrote: User space may not want to overwrite asynchronously changing VCPU event states on write-back. So allow to skip nmi.pending and sipi_vector by setting

Re: [PATCH] KVM: x86: Extend KVM_SET_VCPU_EVENTS with selective updates

2009-12-15 Thread Avi Kivity
On 12/15/2009 06:41 PM, Jan Kiszka wrote: OK, but calling these bits SET makes no sense anymore. What about KVM_VCPUEVENT_VALID_*? Sure. Want to patch? -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line unsubscribe kvm in the

Re: [PATCH] KVM: x86: Extend KVM_SET_VCPU_EVENTS with selective updates

2009-12-14 Thread Jan Kiszka
Jan Kiszka wrote: User space may not want to overwrite asynchronously changing VCPU event states on write-back. So allow to skip nmi.pending and sipi_vector by setting corresponding bits in the flags field of kvm_vcpu_events. What will happen to this patch now? Merge during 2.6.33 window or

Re: [PATCH] KVM: x86: Extend KVM_SET_VCPU_EVENTS with selective updates

2009-12-14 Thread Avi Kivity
On 12/14/2009 12:32 PM, Jan Kiszka wrote: Jan Kiszka wrote: User space may not want to overwrite asynchronously changing VCPU event states on write-back. So allow to skip nmi.pending and sipi_vector by setting corresponding bits in the flags field of kvm_vcpu_events. What will

[PATCH] KVM: x86: Extend KVM_SET_VCPU_EVENTS with selective updates

2009-12-06 Thread Jan Kiszka
User space may not want to overwrite asynchronously changing VCPU event states on write-back. So allow to skip nmi.pending and sipi_vector by setting corresponding bits in the flags field of kvm_vcpu_events. Signed-off-by: Jan Kiszka jan.kis...@siemens.com --- Documentation/kvm/api.txt | 10

Re: [PATCH] KVM: x86: Extend KVM_SET_VCPU_EVENTS with selective updates

2009-12-06 Thread Avi Kivity
On 12/06/2009 06:55 PM, Jan Kiszka wrote: User space may not want to overwrite asynchronously changing VCPU event states on write-back. So allow to skip nmi.pending and sipi_vector by setting corresponding bits in the flags field of kvm_vcpu_events. I think a positive flag (do update nmi

Re: [PATCH] KVM: x86: Extend KVM_SET_VCPU_EVENTS with selective updates

2009-12-06 Thread Jan Kiszka
Avi Kivity wrote: On 12/06/2009 06:55 PM, Jan Kiszka wrote: User space may not want to overwrite asynchronously changing VCPU event states on write-back. So allow to skip nmi.pending and sipi_vector by setting corresponding bits in the flags field of kvm_vcpu_events. I think a positive