Glauber Costa wrote:
On Mon, May 04, 2009 at 05:33:26PM +0300, Avi Kivity wrote:
Glauber Costa wrote:
I'd like to avoid vcpu ioctls from more than one thread, in case we
ever move to a syscall implementation.
Although I don't see exactly what's your point in here.
We're just adding a serialization points through pthreads function, not doing any ioctl from
the outside.
Doesn't the lapic creation call KVM_CREATE_LAPIC?
Oh yeah, that.
Maybe we could then move kvm_vcpu_init to the end of pc_new_cpu.
This way we don't break the separability of pc and x86 concepts. We would then issue the lapic creation
ioctl right after the vcpu is created.
How would you feel about it
Like I said, I'd like to see the lapic creation come from the vcpu thread.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
