RE: RFC: proposal for VM reset hcall

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




> -----Original Message-----
> From: Alexander Graf [mailto:agraf@xxxxxxx]
> Sent: Monday, July 01, 2013 2:46 PM
> To: Yoder Stuart-B08248
> Cc: Wood Scott-B07421; Bhushan Bharat-R65777; kvm@xxxxxxxxxxxxxxx
> Subject: Re: RFC: proposal for VM reset hcall
> 
> 
> 
> Am 01.07.2013 um 19:44 schrieb Yoder Stuart-B08248 <B08248@xxxxxxxxxxxxx>:
> 
> >
> >
> >> -----Original Message-----
> >> From: Wood Scott-B07421
> >> Sent: Monday, July 01, 2013 12:32 PM
> >> To: Yoder Stuart-B08248
> >> Cc: Wood Scott-B07421; Alexander Graf; Bhushan Bharat-R65777; kvm@xxxxxxxxxxxxxxx
> >> Subject: Re: RFC: proposal for VM reset hcall
> >>
> >> 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@xxxxxxxxxxxxxxx
> >>>> 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.
> >
> > Ok, let's get Alex's input as to what shutdown support would
> > look like.  Not sure what a 'shutdown' hcall would do.
> 
> I don't have a strong opinion on whether shutdown is a sub-op of reboot or an individual hcall, but it
> should be there as well :). It certainly makes autotest a lot happier.

If a guest requests a 'shutdown', what is KVM supposed to do?
I'm assuming this means halt the machine / power-down.  Is there
a QEMU exit for this?

Stuart

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux