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_ioctl can be used anywhere, and we guarantee it will
never
be executed outside its realm.
This is not much of a problem, since remote execution is rare. It does happen at
lot at machine bootup, because saving/restoring registers spans a lot of ioctls,
but this should get better if we move to Jan's patch of doing it all at once.
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.
--
error compiling committee.c: too many arguments to function
