Re: [PATCH] KVM: emulator: Only allow VMCALL/VMMCALL trapped by #UD

[Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>]

Dong, Eddie wrote:
> Anthony Liguori wrote:
>   
>> Dong, Eddie wrote:
>>     
>>> Anthony:
>>> 	Actually I am wondering if the binary used for VMMCALL could be
>>> assumed will never be used by Intel processor or vice versa.  BTW,
>>> what is the nenefit to remove hypercall page, which provide more
>>> clean approach IMO? 
>>>
>>>       
>> A hypercall page doesn't help the situation with respect to migration
>> between an AMD and Intel system. 
>>     
>
> I guess I miss something. As if hypercall page is read only after
> creation
> (by VMM), later memory migration won't overlap it. The page could be 
> a "Reserved" in e820 table.
>   

If migration happens while rip is in the hypercall page, and if the 
hypercall page is different in the target host, you may need to apply 
fixups.  The fixups (and the hypercall page itself) may be different 
according to the guest mode (32-bit or 64-bit).

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/