From: Scott Wood <scottwood@freescale.com>
To: Alexander Graf <agraf@suse.de>
Cc: Yoder Stuart-B08248 <B08248@freescale.com>,
Bhushan Bharat-R65777 <R65777@freescale.com>,
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: PPC: RFC: proposal for VM reset & shutdown hcall (v4)
Date: Wed, 3 Jul 2013 14:40:01 -0500 [thread overview]
Message-ID: <1372880401.8183.147@snotra> (raw)
In-Reply-To: <8A260FCA-5E2D-41A0-AD4E-83D41BCC325C@suse.de> (from agraf@suse.de on Wed Jul 3 14:32:07 2013)
On 07/03/2013 02:32:07 PM, Alexander Graf wrote:
>
> On 03.07.2013, at 21:29, Yoder Stuart-B08248 wrote:
>
> > Version 4 changes
> > -clarified that KVM zeros the upper half of the struct fields
> > if the VM is not in 64-bit mode
> >
> >
> ------------------------------------------------------------------------
> > KVM_CAP_EXIT_EPAPR_HCALL Capability
> >
> > A new capability KVM_CAP_EXIT_EPAPR_HCALL is defined to advertise
> > the new KVM_EXIT_EPAPR_HCALL exit .
> >
> >
> ------------------------------------------------------------------------
> > 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.
>
> This still says Power :(. It's either POWER or PowerPC. There is no
> "Power" platform :). As mentioned before, I think "PowerPC" is good
> enough to cover everything.
Tell that to power.org. :-)
That said, in the context of Linux, we still call it powerpc.
-Scott
next prev parent reply other threads:[~2013-07-03 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 19:29 PPC: RFC: proposal for VM reset & shutdown hcall (v4) Yoder Stuart-B08248
2013-07-03 19:32 ` Alexander Graf
2013-07-03 19:40 ` Scott Wood [this message]
2013-07-03 20:16 ` Yoder Stuart-B08248
2013-07-03 21:41 ` 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=1372880401.8183.147@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox