From: Nicholas Piggin <npiggin@gmail.com>
To: linuxppc-dev@lists.ozlabs.org, Vaibhav Jain <vaibhav@linux.ibm.com>
Cc: Laurent Dufour <ldufour@linux.vnet.ibm.com>,
"Aneesh Kumar K . V" <aneesh.kumar@linux.ibm.com>,
Oliver O'Halloran <oohall@gmail.com>,
msuchanek@suse.de, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [DOC][PATCH v2] powerpc: Provide initial documentation for PAPR hcalls
Date: Wed, 28 Aug 2019 19:54:55 +1000 [thread overview]
Message-ID: <1566986020.cw3ahh8v0v.astroid@bobo.none> (raw)
In-Reply-To: <20190828082729.16695-1-vaibhav@linux.ibm.com>
Vaibhav Jain's on August 28, 2019 6:27 pm:
> This doc patch provides an initial description of the hcall op-codes
> that are used by Linux kernel running as a guest (LPAR) on top of
> PowerVM or any other sPAPR compliant hyper-visor (e.g qemu).
>
> Apart from documenting the hcalls the doc-patch also provides a
> rudimentary overview of how hcall ABI, how they are issued with the
> Linux kernel and how information/control flows between the guest and
> hypervisor.
>
> Signed-off-by: Vaibhav Jain <vaibhav@linux.ibm.com>
> ---
> Change-log:
>
> v2:
> * Added a section on Register conventions to be followed when invoking
> hcalls. [Nick]
> * Updated section on HCALL ABI to clarify that byte ordering only
> matters to in/out values passed by a memory buffer. [Laurent]
> * Updated a code comment in 'exceptions-64s.S' describing hypercall
> register conventions to point it to 'papr_hcalls.rst' [Nick]
Thanks for that!
Acked-by: Nicholas Piggin <npiggin@gmail.com>
next prev parent reply other threads:[~2019-08-28 10:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 8:27 [DOC][PATCH v2] powerpc: Provide initial documentation for PAPR hcalls Vaibhav Jain
2019-08-28 9:00 ` Laurent Dufour
2019-08-28 9:54 ` Nicholas Piggin [this message]
2020-02-04 12:01 ` Michael Ellerman
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=1566986020.cw3ahh8v0v.astroid@bobo.none \
--to=npiggin@gmail.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=ldufour@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=msuchanek@suse.de \
--cc=oohall@gmail.com \
--cc=vaibhav@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).