From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH/RFC] Per-architecture hypercall definitions Date: Thu, 11 Oct 2007 14:18:11 +0200 Message-ID: <470E1483.6080808@qumranet.com> References: <200710111406.09439.borntraeger@de.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: Christian Borntraeger Return-path: In-Reply-To: <200710111406.09439.borntraeger-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.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/