On 11/30/2009 01:44 PM, Glauber Costa wrote:
I really dislike this. In general vcpu ioctls are used as components of
some work to be done, for example RMW of some state. In this case it is
meaningless to execute the ioctls remotely, you need to execute the entire
RMW remotely instead.
W
>
> I really dislike this. In general vcpu ioctls are used as components of
> some work to be done, for example RMW of some state. In this case it is
> meaningless to execute the ioctls remotely, you need to execute the entire
> RMW remotely instead.
>
Why? The "M" part of RMW is executed in sha
On 11/26/2009 07:24 PM, Glauber Costa wrote:
This function is similar to qemu-kvm's on_vcpu mechanism. Totally synchronous,
and guarantees that a given function will be executed at the specified vcpu.
The approach I am taking is to put it under the hood, in kvm_vcpu_ioctl.
This way, the kvm_vcpu
This function is similar to qemu-kvm's on_vcpu mechanism. Totally synchronous,
and guarantees that a given function will be executed at the specified vcpu.
The approach I am taking is to put it under the hood, in kvm_vcpu_ioctl.
This way, the kvm_vcpu_ioctl can be used anywhere, and we guarantee i
