On 09/29/14 09:14, Paolo Bonzini wrote:
Il 29/09/2014 14:57, Alexander Graf ha scritto:
Yeah, that would be possible. You do not even need synchronize_state,
it seems to me that it introduces more complication for little gain.
Well, it makes all accels behave the same and keep information always at
a single entity (the env struct). I don't think the vmport code should
have knowledge of a xen env struct.
Yes, we agree on that. In fact the right CPU is already stored in
send_vcpu of XenIOState.
I did reply up the thread because the info is missing here.
Basically current_cpu is NULL here, and I think that no CPU objects
have been created for Xen. So there is no VCPU object to select.
-Don Slutz
Paolo
