Re: RFC: proposal for VM reset hcall

[Scott Wood <scottwood@freescale.com>]

On 07/01/2013 12:28:34 PM, Yoder Stuart-B08248 wrote:
> 
> 
> > -----Original Message-----
> > From: Wood Scott-B07421
> > Sent: Monday, July 01, 2013 11:49 AM
> > To: Yoder Stuart-B08248
> > Cc: Alexander Graf; Wood Scott-B07421; Bhushan Bharat-R65777;  
> kvm@vger.kernel.org
> > Subject: Re: RFC: proposal for VM reset hcall
> >
> > On 07/01/2013 10:56:54 AM, Yoder Stuart-B08248 wrote:
> > > For the e500 PV platform we need a VM reset mechanisms.
> > >
> > > Hypercall: KVM_HC_VM_RESET
> > > Description:  Requests that the virtual machine be reset.  The
> > >               hcall takes no arguments. If successful the hcall  
> does
> > > not
> > >               return.
> > >
> > > Arguments:
> > >      r11    hcall-token   KVM_HC_VM_RESET
> > >
> > > Return values
> > >      r3     status        Status of the hcall.  If the hcall  
> succeeds
> > >                           it does not return.  If an error occurs
> > >                           EV_INTERNAL is returned.
> > >
> > >
> > > Implementation notes:
> > >
> > >    -expect hcall token to be defined with
> > > KVM_HCALL_TOKEN(KVM_HC_VM_RESET)
> > >
> > >    -the KVM_HC_FEATURES hcall should be expanded with a new  
> feature
> > > bit
> > >     to advertise the reset hcall to the VM:  #define
> > > KVM_FEATURE_VM_RESET
> >
> > What about shutdown rather than reset?
> 
> 'Shutdown' means something completely to me than 'reset',
> and doesn't imply a reboot or reset.   I think the name
> should be reset/restart/reboot.

My point is that Alex talked about wanting both reboot and shutdown  
support.  I wasn't suggesting a name change.

-Scott