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
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
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
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
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
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
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
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