From: Scott Wood <scottwood@freescale.com>
To: Yoder Stuart-B08248 <B08248@freescale.com>
Cc: Alexander Graf <agraf@suse.de>,
Wood Scott-B07421 <B07421@freescale.com>,
Bhushan Bharat-R65777 <R65777@freescale.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: RFC: proposal for VM reset hcall
Date: Mon, 1 Jul 2013 11:48:36 -0500 [thread overview]
Message-ID: <1372697316.8183.79@snotra> (raw)
In-Reply-To: <9F6FE96B71CF29479FF1CDC8046E15036324CF@039-SN1MPN1-004.039d.mgd.msft.net> (from B08248@freescale.com on Mon Jul 1 10:56:54 2013)
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?
-Scott
next prev parent reply other threads:[~2013-07-01 16:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 15:56 RFC: proposal for VM reset hcall Yoder Stuart-B08248
2013-07-01 16:48 ` Scott Wood [this message]
2013-07-01 17:28 ` Yoder Stuart-B08248
2013-07-01 17:32 ` Scott Wood
2013-07-01 17:44 ` Yoder Stuart-B08248
2013-07-01 19:45 ` Alexander Graf
2013-07-01 19:58 ` Yoder Stuart-B08248
2013-07-01 20:01 ` Alexander Graf
2013-07-01 20:02 ` Alexander Graf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1372697316.8183.79@snotra \
--to=scottwood@freescale.com \
--cc=B07421@freescale.com \
--cc=B08248@freescale.com \
--cc=R65777@freescale.com \
--cc=agraf@suse.de \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox