Ingo Molnar wrote:
> * Ingo Molnar <[EMAIL PROTECTED]> wrote:
>
>   
>> +/*
>> + * Hypercall calling convention:
>> + *
>> + * RAX is the hypercall index, goes from 0 to __NR_hypercalls-1
>> + *
>> + * Each hypercall may have 0-6 parameters.
>> + *
>> + * parameters 1-6 are in the standard gcc x86_64 calling convention
>> + * order: RDI, RSI, RDX, RCX, R8, R9.
>> + *
>> + * 32-bit parameters are: EDI, ESI, EDX, ECX, EBX, EBP
>> + */
>>     
>
> about the 32-bit side: maybe it gives us a bit more options for later if 
> we pick the natural order for 32-bit too: EBX for index, EAX, EDX, ECX 
> for the first 3 parameters, with the remaining 3 parameters in ESI, EDI, 
> EBP? Most hypercalls will have 0, 1, 2 or 3 parameters.
>   

I don't mind, as long as it's clearly documented.



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


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Reply via email to