Re: [PATCH/RFC] Per-architecture hypercall definitions

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

Christian Borntraeger wrote:
> Currently kvm provides hypercalls only for x86* architectures. To
> provide hypercall infrastructure for other kvm architectures I split
> kvm_para.h into a generic header file and architecture specific
> definitions.
> Currently there are definitions for s390 (experimental, ABI not final,
> and I still have to find out how to get an assigned diagnose number)
> and x86. I already made the split using the common x86 architecture
> folder that will hit 2.6.24-rc soon. 
>
>   
Looks good.  I'll commit (minus the s390 part) once the x86 merge is 
behind us.


> One point for discussion:
>
> i386 only supports up to 4 parameters. On s390 I coded definitions for
> up to 6 parameters. Are we going to limit kvm to 4 parameters?
>   

I guess we can add more parameters if the need arises.  We don't clobber 
registers so there's no issue with that.



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


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/