On 07/02/2013 10:33:58 AM, Yoder Stuart-B08248 wrote:
> -----Original Message-----
> From: Alexander Graf [mailto:agraf@xxxxxxx]
> Sent: Tuesday, July 02, 2013 10:23 AM
> To: Yoder Stuart-B08248
> Cc: Bhushan Bharat-R65777; Wood Scott-B07421; kvm@xxxxxxxxxxxxxxx
list; kvm-ppc@xxxxxxxxxxxxxxx
> Subject: Re: RFC: proposal for VM reset & shutdown hcall (v2)
>
> On 07/02/2013 05:07 PM, Yoder Stuart-B08248 wrote:
> >
------------------------------------------------------------------------
> > Advertising reset and shutdown in device tree.
> >
> > A virtual machine can detect the availability of the reset
> > and shutdown hcalls by looking at properties on the /hypervisor
> > node.
> >
> > Property name: has-reset
>
> I don't remember how ePAPR specifies this. Aren't keys in
/hypervisor
> supposed to be common throughout hypervisors? So if Windriver wants
to
> add a reset hypercall, they'd also add "has-reset"? How does the
guest
> know which hcall number to issue?
ePAPR does not define how additional hypervisor specific properties
are defined.
Since these are KVM-specific hcalls we should probably not name these
generically and call them kvm-has-reset and kvm-has-shutdown.
kvm,has-reset and kvm,has-shutdown would be more stylistically correct.
This assumes that we're going to put this in Documentation/virtual/kvm/
-- otherwise the prefix should be "qemu".
-Scott
--
To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
