From: Gleb Natapov <gleb@redhat.com>
To: Bharat Bhushan <r65777@freescale.com>
Cc: kvm@vger.kernel.org, kvm-ppc@vger.kernel.org, agraf@suse.de,
scottwood@freescale.com, stuart.yoder@freescale.com,
Bharat Bhushan <Bharat.Bhushan@freescale.com>
Subject: Re: [PATCH 3/5] booke: define reset and shutdown hcalls
Date: Mon, 15 Jul 2013 14:30:20 +0300 [thread overview]
Message-ID: <20130715113020.GQ11772@redhat.com> (raw)
In-Reply-To: <1373886679-19581-4-git-send-email-Bharat.Bhushan@freescale.com>
On Mon, Jul 15, 2013 at 04:41:17PM +0530, Bharat Bhushan wrote:
> KVM_HC_VM_RESET: Requests that the virtual machine be reset.
> KVM_HC_VM_SHUTDOWN: Requests that the virtual machine be powered-off/halted.
>
> These hcalls are handled by guest userspace.
>
> Signed-off-by: Bharat Bhushan <bharat.bhushan@freescale.com>
> ---
> Documentation/virtual/kvm/hypercalls.txt | 16 ++++++++++++++++
> include/uapi/linux/kvm_para.h | 3 ++-
> 2 files changed, 18 insertions(+), 1 deletions(-)
>
> diff --git a/Documentation/virtual/kvm/hypercalls.txt b/Documentation/virtual/kvm/hypercalls.txt
> index ea113b5..58acdc1 100644
> --- a/Documentation/virtual/kvm/hypercalls.txt
> +++ b/Documentation/virtual/kvm/hypercalls.txt
> @@ -64,3 +64,19 @@ Purpose: To enable communication between the hypervisor and guest there is a
> shared page that contains parts of supervisor visible register state.
> The guest can map this shared page to access its supervisor register through
> memory using this hypercall.
> +
> +5. KVM_HC_VM_RESET
> +------------------------
> +Architecture: PPC
> +Status: active
> +Purpose: Requests that the virtual machine be reset. The hcall takes no
> +arguments. If successful the hcall does not return. If an error occurs it
> +returns EV_INTERNAL.
> +
> +6. KVM_HC_VM_SHUTDOWN
> +------------------------
> +Architecture: PPC
> +Status: active
> +Purpose: Requests that the virtual machine be powered-off/halted.
> +The hcall takes no arguments. If successful the hcall does not return.
> +If an error occurs it returns EV_INTERNAL.
> diff --git a/include/uapi/linux/kvm_para.h b/include/uapi/linux/kvm_para.h
> index cea2c5c..218882d 100644
> --- a/include/uapi/linux/kvm_para.h
> +++ b/include/uapi/linux/kvm_para.h
> @@ -19,7 +19,8 @@
> #define KVM_HC_MMU_OP 2
> #define KVM_HC_FEATURES 3
> #define KVM_HC_PPC_MAP_MAGIC_PAGE 4
> -
> +#define KVM_HC_VM_RESET 5
> +#define KVM_HC_VM_SHUTDOWN 6
There is no much sense to share hypercalls between architectures. There
is zero probability x86 will implement those for instance (not sure
why PPC will want them either instead of emulating devices that do
shutdown/reset). So lets move them to arch headers.
--
Gleb.
next prev parent reply other threads:[~2013-07-15 11:30 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 11:11 [PATCH 0/5] powerpc: implement reset/shutdown hcalls Bharat Bhushan
2013-07-15 11:11 ` [PATCH 1/5] powerpc: define ePAPR hcall exit interface Bharat Bhushan
2013-07-15 11:21 ` Alexander Graf
2013-07-15 11:32 ` Bhushan Bharat-R65777
2013-07-15 11:11 ` [PATCH 2/5] booke: exit to guest userspace for unimplemented hcalls in kvm Bharat Bhushan
2013-07-15 11:31 ` Alexander Graf
2013-07-15 11:38 ` Bhushan Bharat-R65777
2013-07-15 11:46 ` Alexander Graf
2013-07-15 14:50 ` Bhushan Bharat-R65777
2013-07-15 14:56 ` Alexander Graf
2013-07-15 15:13 ` Bhushan Bharat-R65777
2013-07-15 15:29 ` Alexander Graf
2013-07-15 15:35 ` Bhushan Bharat-R65777
2013-07-15 15:38 ` Alexander Graf
2013-07-15 18:07 ` Scott Wood
2013-07-16 4:46 ` Bhushan Bharat-R65777
2013-07-15 11:11 ` [PATCH 3/5] booke: define reset and shutdown hcalls Bharat Bhushan
2013-07-15 11:30 ` Gleb Natapov [this message]
2013-07-15 11:44 ` Alexander Graf
2013-07-15 12:15 ` Gleb Natapov
2013-07-15 12:21 ` Alexander Graf
2013-07-15 12:24 ` Gleb Natapov
2013-07-15 12:26 ` Alexander Graf
2013-07-15 12:31 ` Gleb Natapov
2013-07-15 18:17 ` Scott Wood
2013-07-16 6:35 ` Gleb Natapov
2013-07-16 23:04 ` Scott Wood
2013-07-17 11:00 ` Gleb Natapov
2013-07-17 12:19 ` Alexander Graf
2013-07-17 15:19 ` Yoder Stuart-B08248
2013-07-17 15:21 ` Alexander Graf
2013-07-17 15:36 ` Yoder Stuart-B08248
2013-07-17 15:41 ` Alexander Graf
2013-07-17 15:47 ` Bhushan Bharat-R65777
2013-07-17 15:52 ` Alexander Graf
2013-07-17 15:59 ` Bhushan Bharat-R65777
2013-07-17 16:04 ` Alexander Graf
2013-07-17 16:21 ` Bhushan Bharat-R65777
2013-07-17 16:23 ` Alexander Graf
2013-07-17 16:59 ` Scott Wood
2013-07-17 17:05 ` Alexander Graf
2013-07-17 17:09 ` Scott Wood
2013-07-15 11:11 ` [PATCH 4/5] powerpc: Resolve KVM_HC_FEATURES compilation dependeny Bharat Bhushan
2013-07-15 11:46 ` Alexander Graf
2013-07-15 11:11 ` [PATCH 5/5] powerpc: using reset hcall when kvm,has-reset Bharat Bhushan
2013-07-15 11:50 ` Alexander Graf
2013-07-15 15:05 ` Bhushan Bharat-R65777
2013-07-15 15:09 ` Alexander Graf
2013-07-15 15:16 ` Bhushan Bharat-R65777
2013-07-15 18:21 ` Scott Wood
2013-07-15 20:28 ` Alexander Graf
2013-07-15 20:52 ` Scott Wood
2013-07-15 20:55 ` Alexander Graf
2013-07-15 22:23 ` Scott Wood
2013-07-16 23:21 ` Alexander Graf
2013-07-16 23:26 ` Scott Wood
2013-07-16 23:37 ` Scott Wood
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=20130715113020.GQ11772@redhat.com \
--to=gleb@redhat.com \
--cc=Bharat.Bhushan@freescale.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=r65777@freescale.com \
--cc=scottwood@freescale.com \
--cc=stuart.yoder@freescale.com \
/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