On 9 August 2013 08:35, Rusty Russell <ru...@rustcorp.com.au> wrote: > That's a lot of replumbing and indirect function calls for a fairly > obscure case. We certainly don't have a nice CPUState lying around in > virtio at the moment, for example.
Actually if you're in an IO routine you do: it will be in the global variable 'current_cpu'. Most IO functions don't need this, but it's what we use for things like "this device behaviour varies depending on which CPU accesses it". -- PMM
