From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott Wood Date: Tue, 02 Jul 2013 22:13:20 +0000 Subject: Re: RFC: proposal for VM reset & shutdown hcall (v3) Message-Id: <1372803200.8183.123@snotra> List-Id: References: <9F6FE96B71CF29479FF1CDC8046E150363342F@039-SN1MPN1-004.039d.mgd.msft.net> In-Reply-To: <9F6FE96B71CF29479FF1CDC8046E150363342F@039-SN1MPN1-004.039d.mgd.msft.net> (from B08248@freescale.com on Tue Jul 2 17:08:02 2013) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Yoder Stuart-B08248 Cc: Bhushan Bharat-R65777 , Alexander Graf , Wood Scott-B07421 , "kvm@vger.kernel.org list" , "kvm-ppc@vger.kernel.org" On 07/02/2013 05:08:02 PM, Yoder Stuart-B08248 wrote: > ------------------------------------------------------------------------ > KVM_EXIT_EPAPR_HCALL exit definition > > /* KVM_EXIT_EPAPR_HCALL */ > struct { > __u64 nr; > __u64 ret; > __u64 args[8]; > } epapr_hcall; > > This is used on Power/PowerPC platforms that support ePAPR hcalls. > It occurs when a guest does a hypercall (as defined > in the ePAPR 1.1) and the hcall is not handled by the kernel. > > The 'nr' field contains the hypercall number (from the guest R11), > and 'args' contains the arguments (from the guest R3 - R10). > Userspace should put the return code in 'ret' and any extra returned > values in args[]. As per the ePAPR hcall ABI, the return value > should be returned to the guest in R3 and output return values > in R4 - R10. Should we specify that KVM fills in upper half of each value with zero if the target is not in 64-bit mode? -Scott From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott Wood Subject: Re: RFC: proposal for VM reset & shutdown hcall (v3) Date: Tue, 2 Jul 2013 17:13:20 -0500 Message-ID: <1372803200.8183.123@snotra> References: <9F6FE96B71CF29479FF1CDC8046E150363342F@039-SN1MPN1-004.039d.mgd.msft.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; delsp=Yes; format=Flowed Content-Transfer-Encoding: 8BIT Cc: Bhushan Bharat-R65777 , Alexander Graf , Wood Scott-B07421 , "kvm@vger.kernel.org list" , "kvm-ppc@vger.kernel.org" To: Yoder Stuart-B08248 Return-path: In-Reply-To: <9F6FE96B71CF29479FF1CDC8046E150363342F@039-SN1MPN1-004.039d.mgd.msft.net> (from B08248@freescale.com on Tue Jul 2 17:08:02 2013) Content-Disposition: inline Sender: kvm-ppc-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 07/02/2013 05:08:02 PM, Yoder Stuart-B08248 wrote: > ------------------------------------------------------------------------ > KVM_EXIT_EPAPR_HCALL exit definition > > /* KVM_EXIT_EPAPR_HCALL */ > struct { > __u64 nr; > __u64 ret; > __u64 args[8]; > } epapr_hcall; > > This is used on Power/PowerPC platforms that support ePAPR hcalls. > It occurs when a guest does a hypercall (as defined > in the ePAPR 1.1) and the hcall is not handled by the kernel. > > The 'nr' field contains the hypercall number (from the guest R11), > and 'args' contains the arguments (from the guest R3 - R10). > Userspace should put the return code in 'ret' and any extra returned > values in args[]. As per the ePAPR hcall ABI, the return value > should be returned to the guest in R3 and output return values > in R4 - R10. Should we specify that KVM fills in upper half of each value with zero if the target is not in 64-bit mode? -Scott