Re: Cpu pools discussion

[Juergen Gross <juergen.gross@ts.fujitsu.com>]

Keir Fraser wrote:
> On 28/07/2009 06:40, "Juergen Gross" <juergen.gross@ts.fujitsu.com> wrote:
> 
>> BTW: continue_hypercall_on_cpu() exists on x86 only and it isn't really much
>> better than my usage of it:
>> - remember old pinning state of current vcpu
>> - pin it temporarily to the cpu it should continue on
>> - continue the hypercall
>> - remove temporary pinning
>> - re-establish old pinning (if any)
>> Pretty much the same as my solution above ;-)
> 
> If your solution locks the pinning, as we do already, so that it cannot be
> changed while the continue_hypercall_on_cpu() is running, then that is fine.
> If it's not locked then it's not safe.

Locking in my solution should be okay.


Juergen

-- 
Juergen Gross                 Principal Developer Operating Systems
TSP ES&S SWE OS6                       Telephone: +49 (0) 89 636 47950
Fujitsu Technolgy Solutions               e-mail: juergen.gross@ts.fujitsu.com
Otto-Hahn-Ring 6                        Internet: ts.fujitsu.com
D-81739 Muenchen                 Company details: ts.fujitsu.com/imprint.html