From: Scott Wood <scottwood@freescale.com>
To: Yoder Stuart-B08248 <B08248@freescale.com>
Cc: Bhushan Bharat-R65777 <R65777@freescale.com>,
Alexander Graf <agraf@suse.de>,
Wood Scott-B07421 <B07421@freescale.com>,
"kvm@vger.kernel.org list" <kvm@vger.kernel.org>,
"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>
Subject: Re: RFC: proposal for VM reset & shutdown hcall (v3)
Date: Tue, 02 Jul 2013 22:13:20 +0000 [thread overview]
Message-ID: <1372803200.8183.123@snotra> (raw)
In-Reply-To: <9F6FE96B71CF29479FF1CDC8046E150363342F@039-SN1MPN1-004.039d.mgd.msft.net> (from B08248@freescale.com on Tue Jul 2 17:08:02 2013)
On 07/02/2013 05:08:02 PM, Yoder Stuart-B08248 wrote:
> ------------------------------------------------------------------------
> KVM_EXIT_EPAPR_HCALL exit definition
>
> /* KVM_EXIT_EPAPR_HCALL */
> struct {
> __u64 nr;
> __u64 ret;
> __u64 args[8];
> } epapr_hcall;
>
> This is used on Power/PowerPC platforms that support ePAPR hcalls.
> It occurs when a guest does a hypercall (as defined
> in the ePAPR 1.1) and the hcall is not handled by the kernel.
>
> The 'nr' field contains the hypercall number (from the guest R11),
> and 'args' contains the arguments (from the guest R3 - R10).
> Userspace should put the return code in 'ret' and any extra returned
> values in args[]. As per the ePAPR hcall ABI, the return value
> should be returned to the guest in R3 and output return values
> in R4 - R10.
Should we specify that KVM fills in upper half of each value with zero
if the target is not in 64-bit mode?
-Scott
WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: Yoder Stuart-B08248 <B08248@freescale.com>
Cc: Bhushan Bharat-R65777 <R65777@freescale.com>,
Alexander Graf <agraf@suse.de>,
Wood Scott-B07421 <B07421@freescale.com>,
"kvm@vger.kernel.org list" <kvm@vger.kernel.org>,
"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>
Subject: Re: RFC: proposal for VM reset & shutdown hcall (v3)
Date: Tue, 2 Jul 2013 17:13:20 -0500 [thread overview]
Message-ID: <1372803200.8183.123@snotra> (raw)
In-Reply-To: <9F6FE96B71CF29479FF1CDC8046E150363342F@039-SN1MPN1-004.039d.mgd.msft.net> (from B08248@freescale.com on Tue Jul 2 17:08:02 2013)
On 07/02/2013 05:08:02 PM, Yoder Stuart-B08248 wrote:
> ------------------------------------------------------------------------
> KVM_EXIT_EPAPR_HCALL exit definition
>
> /* KVM_EXIT_EPAPR_HCALL */
> struct {
> __u64 nr;
> __u64 ret;
> __u64 args[8];
> } epapr_hcall;
>
> This is used on Power/PowerPC platforms that support ePAPR hcalls.
> It occurs when a guest does a hypercall (as defined
> in the ePAPR 1.1) and the hcall is not handled by the kernel.
>
> The 'nr' field contains the hypercall number (from the guest R11),
> and 'args' contains the arguments (from the guest R3 - R10).
> Userspace should put the return code in 'ret' and any extra returned
> values in args[]. As per the ePAPR hcall ABI, the return value
> should be returned to the guest in R3 and output return values
> in R4 - R10.
Should we specify that KVM fills in upper half of each value with zero
if the target is not in 64-bit mode?
-Scott
next prev parent reply other threads:[~2013-07-02 22:13 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 21:59 RFC: proposal for VM reset & shutdown hcall Yoder Stuart-B08248
2013-07-01 22:13 ` Alexander Graf
2013-07-01 22:13 ` Alexander Graf
2013-07-01 22:59 ` Yoder Stuart-B08248
2013-07-01 22:59 ` Yoder Stuart-B08248
2013-07-01 23:01 ` Alexander Graf
2013-07-01 23:01 ` Alexander Graf
2013-07-01 23:05 ` Yoder Stuart-B08248
2013-07-01 23:05 ` Yoder Stuart-B08248
2013-07-01 23:09 ` Scott Wood
2013-07-01 23:09 ` Scott Wood
2013-07-01 23:12 ` Alexander Graf
2013-07-01 23:12 ` Alexander Graf
2013-07-01 23:11 ` Alexander Graf
2013-07-01 23:11 ` Alexander Graf
2013-07-01 23:02 ` Yoder Stuart-B08248
2013-07-01 23:02 ` Yoder Stuart-B08248
2013-07-02 15:07 ` RFC: proposal for VM reset & shutdown hcall (v2) Yoder Stuart-B08248
2013-07-02 15:07 ` Yoder Stuart-B08248
2013-07-02 15:23 ` Alexander Graf
2013-07-02 15:23 ` Alexander Graf
2013-07-02 15:33 ` Yoder Stuart-B08248
2013-07-02 15:33 ` Yoder Stuart-B08248
2013-07-02 16:56 ` Scott Wood
2013-07-02 16:56 ` Scott Wood
2013-07-02 19:11 ` Yoder Stuart-B08248
2013-07-02 19:11 ` Yoder Stuart-B08248
2013-07-02 22:08 ` RFC: proposal for VM reset & shutdown hcall (v3) Yoder Stuart-B08248
2013-07-02 22:08 ` Yoder Stuart-B08248
2013-07-02 22:13 ` Scott Wood [this message]
2013-07-02 22:13 ` Scott Wood
2013-07-02 22:19 ` Alexander Graf
2013-07-02 22:19 ` 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=1372803200.8183.123@snotra \
--to=scottwood@freescale.com \
--cc=B07421@freescale.com \
--cc=B08248@freescale.com \
--cc=R65777@freescale.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.