From: Haren Myneni <haren@linux.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
linuxppc-dev@lists.ozlabs.org, linux-crypto@vger.kernel.org,
herbert@gondor.apana.org.au, npiggin@gmail.com
Subject: Re: [PATCH v4 09/16] powerpc/pseries/vas: Add HCALL wrappers for VAS handling
Date: Fri, 04 Jun 2021 14:53:06 -0700 [thread overview]
Message-ID: <93586baca94d10ec5658d547b109aaa6a55ff635.camel@linux.ibm.com> (raw)
In-Reply-To: <87o8clg83d.fsf@mpe.ellerman.id.au>
On Fri, 2021-06-04 at 21:52 +1000, Michael Ellerman wrote:
> Haren Myneni <haren@linux.ibm.com> writes:
> > This patch adds the following HCALL wrapper functions to allocate,
>
> Normal spelling is "hcall".
>
> > modify and deallocate VAS windows, and retrieve VAS capabilities.
> >
> > H_ALLOCATE_VAS_WINDOW: Allocate VAS window
> > H_DEALLOCATE_VAS_WINDOW: Close VAS window
> > H_MODIFY_VAS_WINDOW: Setup window before using
> > H_QUERY_VAS_CAPABILITIES: Get VAS capabilities
>
> Please tell us which version of PAPR, and in which section etc.,
> these
> are described in.
>
> > Signed-off-by: Haren Myneni <haren@linux.ibm.com>
> > Reviewed-by: Nicholas Piggin <npiggin@gmail.com>
> > ---
> > arch/powerpc/platforms/pseries/vas.c | 217
> > +++++++++++++++++++++++++++
> > 1 file changed, 217 insertions(+)
> > create mode 100644 arch/powerpc/platforms/pseries/vas.c
> >
> > diff --git a/arch/powerpc/platforms/pseries/vas.c
> > b/arch/powerpc/platforms/pseries/vas.c
> > new file mode 100644
> > index 000000000000..06960151477c
> > --- /dev/null
> > +++ b/arch/powerpc/platforms/pseries/vas.c
> > @@ -0,0 +1,217 @@
> > +// SPDX-License-Identifier: GPL-2.0-or-later
> > +/*
> > + * Copyright 2020-21 IBM Corp.
> > + */
> > +
> > +#define pr_fmt(fmt) "vas: " fmt
> > +
> > +#include <linux/module.h>
> > +#include <linux/kernel.h>
> > +#include <linux/export.h>
> > +#include <linux/types.h>
> > +#include <linux/delay.h>
> > +#include <linux/slab.h>
> > +#include <linux/irqdomain.h>
> > +#include <linux/interrupt.h>
> > +#include <linux/sched/mm.h>
> > +#include <linux/mmu_context.h>
> > +#include <asm/hvcall.h>
> > +#include <asm/hvconsole.h>
> > +#include <asm/machdep.h>
>
> Do we need all those headers?
>
> > +#include <asm/plpar_wrappers.h>
> > +#include <asm/vas.h>
> > +#include "vas.h"
> > +
> > +#define VAS_INVALID_WIN_ADDRESS 0xFFFFFFFFFFFFFFFFul
> > +#define VAS_DEFAULT_DOMAIN_ID 0xFFFFFFFFFFFFFFFFul
>
> Some blank lines for formatting please.
>
> > +/* Authority Mask Register (AMR) value is not supported in */
> > +/* linux implementation. So pass '0' to modify window HCALL */
>
> Please fix the comment formatting.
>
> > +#define VAS_AMR_VALUE 0
>
> This is only used in one place. It'd be simpler to just pass 0 and
> move
> the comment there.
>
> > +/* phyp allows one credit per window right now */
> > +#define DEF_WIN_CREDS 1
> > +
> > +static int64_t hcall_return_busy_check(int64_t rc)
> > +{
>
> Please use normal kernel types, ie. s64, or just long.
>
> Same comment throughout.
>
> > + /* Check if we are stalled for some time */
> > + if (H_IS_LONG_BUSY(rc)) {
> > + msleep(get_longbusy_msecs(rc));
> > + rc = H_BUSY;
> > + } else if (rc == H_BUSY) {
> > + cond_resched();
> > + }
> > +
> > + return rc;
> > +}
> > +
> > +/*
> > + * Allocate VAS window HCALL
> > + */
> > +static int plpar_vas_allocate_window(struct vas_window *win, u64
> > *domain,
> > + u8 wintype, u16 credits)
>
> You don't have to use the "plpar" prefix for these sort of wrappers.
>
> Just naming them after the hcall would probably be clearer, so:
>
> h_allocate_vas_window(... )
>
> > +{
> > + long retbuf[PLPAR_HCALL9_BUFSIZE] = {0};
> > + int64_t rc;
> > +
> > + do {
> > + rc = plpar_hcall9(H_ALLOCATE_VAS_WINDOW, retbuf,
> > wintype,
> > + credits, domain[0], domain[1],
> > domain[2],
> > + domain[3], domain[4], domain[5]);
> > +
> > + rc = hcall_return_busy_check(rc);
> > + } while (rc == H_BUSY);
> > +
> > + switch (rc) {
> > + case H_SUCCESS:
> > + win->winid = retbuf[0];
> > + win->lpar.win_addr = retbuf[1];
> > + win->lpar.complete_irq = retbuf[2];
> > + win->lpar.fault_irq = retbuf[3];
>
> You shouldn't mutate win until you know there is no error.
>
> > + if (win->lpar.win_addr == VAS_INVALID_WIN_ADDRESS) {
> > + pr_err("HCALL(%x): COPY/PASTE is not
> > supported\n",
> > + H_ALLOCATE_VAS_WINDOW);
> > + return -ENOTSUPP;
> > + }
> > + return 0;
> > + case H_PARAMETER:
> > + pr_err("HCALL(%x): Invalid window type (%u)\n",
> > + H_ALLOCATE_VAS_WINDOW, wintype);
> > + return -EINVAL;
> > + case H_P2:
> > + pr_err("HCALL(%x): Credits(%u) exceed maximum window
> > credits\n",
> > + H_ALLOCATE_VAS_WINDOW, credits);
> > + return -EINVAL;
> > + case H_COP_HW:
> > + pr_err("HCALL(%x): User-mode COPY/PASTE is not
> > supported\n",
> > + H_ALLOCATE_VAS_WINDOW);
> > + return -ENOTSUPP;
> > + case H_RESOURCE:
> > + pr_err("HCALL(%x): LPAR credit limit exceeds window
> > limit\n",
> > + H_ALLOCATE_VAS_WINDOW);
> > + return -EPERM;
> > + case H_CONSTRAINED:
> > + pr_err("HCALL(%x): Credits (%u) are not available\n",
> > + H_ALLOCATE_VAS_WINDOW, credits);
> > + return -EPERM;
> > + default:
> > + pr_err("HCALL(%x): Unexpected error %lld\n",
> > + H_ALLOCATE_VAS_WINDOW, rc);
> > + return -EIO;
> > + }
>
> Do we really need all these error prints? It's very verbose, and
> presumably in normal operation none of these are meant to happen
> anyway.
>
> Can't we just have a single case that prints the error value?
Right, generally we should not see these errors. But few of them are
failures based on argument(s) passing to hcall. like passing invalid
window type or credits are not availavble.
So can I add error messages for these specific ones and common error
message for other failures with the error code?
case H_PARAMETER:
pr_err("HCALL(%x): Invalid window type (%u)\n",
H_ALLOCATE_VAS_WINDOW, wintype);
case H_CONSTRAINED:
pr_err("HCALL(%x): Credits (%u) are not available\n",
H_ALLOCATE_VAS_WINDOW, credits);
case H_P2:
pr_err("HCALL(%x): Credits(%u) exceed maximum window
credits\n", H_ALLOCATE_VAS_WINDOW, credits);
default:
pr_err("HCALL(%x): failure with error code %d\n",
H_ALLOCATE_VAS_WINDOW, rc);
>
> Same comment for the other hcalls.
>
> > +}
> > +
> > +/*
> > + * Deallocate VAS window HCALL.
> > + */
> > +static int plpar_vas_deallocate_window(u64 winid)
> > +{
> > + int64_t rc;
> > +
> > + do {
> > + rc = plpar_hcall_norets(H_DEALLOCATE_VAS_WINDOW,
> > winid);
> > +
> > + rc = hcall_return_busy_check(rc);
> > + } while (rc == H_BUSY);
> > +
> > + switch (rc) {
> > + case H_SUCCESS:
> > + return 0;
> > + case H_PARAMETER:
> > + pr_err("HCALL(%x): Invalid window ID %llu\n",
> > + H_DEALLOCATE_VAS_WINDOW, winid);
> > + return -EINVAL;
> > + case H_STATE:
> > + pr_err("HCALL(%x): Window(%llu): Invalid page table
> > entries\n",
> > + H_DEALLOCATE_VAS_WINDOW, winid);
> > + return -EPERM;
> > + default:
> > + pr_err("HCALL(%x): Unexpected error %lld for
> > window(%llu)\n",
> > + H_DEALLOCATE_VAS_WINDOW, rc, winid);
> > + return -EIO;
> > + }
> > +}
> > +
> > +/*
> > + * Modify VAS window.
> > + * After the window is opened with allocate window HCALL,
> > configure it
> > + * with flags and LPAR PID before using.
> > + */
> > +static int plpar_vas_modify_window(struct vas_window *win)
> > +{
> > + int64_t rc;
> > + u32 lpid = mfspr(SPRN_PID);
>
> The lpid would be SPRN_LPID ?
> But you can't read it from a guest. Is the variable just misnamed?
yes, not using in pseries code now, but thought LPID is available in
SPRN_PID - PIDR is SPR48 and access to that in LPAR. Not true?
"processId : The LPAR process ID to bind to the specified window. This
parameter is ignored if the “closeWindow” flag is set.
threadId : The LPAR thread ID to bind to the specified window. This
parameter is ignored if the “closeWindow”
flag is set."
since TIDR is deprecated on p10, we are not passing threadID
>
> > +
> > + /*
> > + * AMR value is not supported in Linux implementation
> > + * phyp ignores it if 0 is passed.
> > + */
>
> Heh, this comment is already here.
>
> Do you mean the Linux VAS implementation doesn't support AMR? Because
> Linux definitely does use AMR.
Linux VAS implementation does not support AMR. The application /
library has to pass this value with TX_WIN_OPEN ioctl. We do not have
any use case right now. I will change the above comment to make it
clear.
phyp added this interface for future reference and AIX may be using it.
Thanks
Haren
>
> > + do {
> > + rc = plpar_hcall_norets(H_MODIFY_VAS_WINDOW, win-
> > >winid,
> > + lpid, 0, VAS_MOD_WIN_FLAGS,
> > + VAS_AMR_VALUE);
> > +
> > + rc = hcall_return_busy_check(rc);
> > + } while (rc == H_BUSY);
> > +
> > + switch (rc) {
> > + case H_SUCCESS:
> > + return 0;
> > + case H_PARAMETER:
> > + pr_err("HCALL(%x): Invalid window ID %u\n",
> > + H_MODIFY_VAS_WINDOW, win->winid);
> > + return -EINVAL;
> > + case H_P2:
> > + pr_err("HCALL(%x): Window(%d): Invalid LPAR Process ID
> > %u\n",
> > + H_MODIFY_VAS_WINDOW, lpid, win->winid);
> > + return -EINVAL;
> > + case H_P3:
> > + /* LPAR thread ID is deprecated on P10 */
> > + pr_err("HCALL(%x): Invalid LPAR Thread ID for
> > window(%u)\n",
> > + H_MODIFY_VAS_WINDOW, win->winid);
> > + return -EINVAL;
> > + case H_STATE:
> > + pr_err("HCALL(%x): Jobs in progress, Can't modify
> > window(%u)\n",
> > + H_MODIFY_VAS_WINDOW, win->winid);
> > + return -EBUSY;
> > + default:
> > + pr_err("HCALL(%x): Unexpected error %lld for
> > window(%u)\n",
> > + H_MODIFY_VAS_WINDOW, rc, win->winid);
> > + return -EIO;
> > + }
> > +}
> > +
> > +/*
> > + * This HCALL is used to determine the capabilities that pHyp
> > provides.
> > + * @hcall: H_QUERY_VAS_CAPABILITIES or H_QUERY_NX_CAPABILITIES
> > + * @query_type: If 0 is passed, phyp returns the overall
> > capabilities
> > + * which provides all feature(s) that are available. Then
> > + * query phyp to get the corresponding capabilities for
> > + * the specific feature.
> > + * Example: H_QUERY_VAS_CAPABILITIES provides VAS GZIP QoS
> > + * and VAS GZIP Default capabilities.
> > + * H_QUERY_NX_CAPABILITIES provides NX GZIP
> > + * capabilities.
> > + * @result: Return buffer to save capabilities.
> > + */
> > +int plpar_vas_query_capabilities(const u64 hcall, u8 query_type,
> > + u64 result)
> > +{
> > + int64_t rc;
> > +
> > + rc = plpar_hcall_norets(hcall, query_type, result);
> > +
> > + switch (rc) {
> > + case H_SUCCESS:
> > + return 0;
> > + case H_PARAMETER:
> > + pr_err("HCALL(%llx): Invalid query type %u\n", hcall,
> > + query_type);
> > + return -EINVAL;
> > + case H_PRIVILEGE:
> > + pr_err("HCALL(%llx): Invalid result buffer 0x%llx\n",
> > + hcall, result);
> > + return -EACCES;
> > + default:
> > + pr_err("HCALL(%llx): Unexpected error %lld\n", hcall,
> > rc);
> > + return -EIO;
> > + }
> > +}
>
> cheers
next prev parent reply other threads:[~2021-06-04 21:53 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 9:25 [PATCH v4 00/16] Enable VAS and NX-GZIP support on powerVM Haren Myneni
2021-05-21 9:28 ` [PATCH v4 01/16] powerpc/vas: Move VAS API to book3s common platform Haren Myneni
2021-06-03 3:32 ` Nicholas Piggin
2021-06-03 20:23 ` Haren Myneni
2021-05-21 9:29 ` [PATCH v4 02/16] powerpc/powernv/vas: Rename register/unregister functions Haren Myneni
2021-05-21 9:30 ` [PATCH v4 03/16] powerpc/vas: Add platform specific user window operations Haren Myneni
2021-06-03 4:05 ` Nicholas Piggin
2021-06-03 20:25 ` Haren Myneni
2021-05-21 9:31 ` [PATCH v4 04/16] powerpc/vas: Create take/drop pid and mm references Haren Myneni
2021-06-03 4:21 ` Nicholas Piggin
2021-06-04 4:08 ` Haren Myneni
2021-06-05 0:31 ` Nicholas Piggin
2021-06-05 3:03 ` Nicholas Piggin
2021-05-21 9:32 ` [PATCH v4 05/16] powerpc/vas: Move update_csb/dump_crb to common book3s platform Haren Myneni
2021-06-03 4:26 ` Nicholas Piggin
2021-05-21 9:33 ` [PATCH v4 06/16] powerpc/vas: Define and use common vas_window struct Haren Myneni
2021-06-03 4:38 ` Nicholas Piggin
2021-06-04 4:35 ` Haren Myneni
2021-06-04 11:52 ` Michael Ellerman
2021-06-04 21:19 ` Haren Myneni
2021-05-21 9:34 ` [PATCH v4 07/16] powerpc/pseries/vas: Define VAS/NXGZIP HCALLs and structs Haren Myneni
2021-06-03 4:47 ` Nicholas Piggin
2021-06-04 1:30 ` Haren Myneni
2021-06-05 0:37 ` Nicholas Piggin
2021-05-21 9:34 ` [PATCH v4 08/16] powerpc/vas: Define QoS credit flag to allocate window Haren Myneni
2021-05-21 9:35 ` [PATCH v4 09/16] powerpc/pseries/vas: Add HCALL wrappers for VAS handling Haren Myneni
2021-06-04 11:52 ` Michael Ellerman
2021-06-04 21:53 ` Haren Myneni [this message]
2021-05-21 9:38 ` [PATCH v4 10/16] powerpc/pseries/vas: Implement getting capabilities from hypervisor Haren Myneni
2021-05-21 9:39 ` [PATCH v4 11/16] powerpc/pseries/vas: Integrate API with open/close windows Haren Myneni
2021-05-21 9:39 ` [PATCH v4 12/16] powerpc/pseries/vas: Setup IRQ and fault handling Haren Myneni
2021-06-03 5:48 ` Nicholas Piggin
2021-06-04 1:19 ` Haren Myneni
2021-06-05 0:43 ` Nicholas Piggin
2021-05-21 9:40 ` [PATCH v4 13/16] crypto/nx: Rename nx-842-pseries file name to nx-common-pseries Haren Myneni
2021-05-21 9:41 ` [PATCH v4 14/16] crypto/nx: Register and unregister VAS interface Haren Myneni
2021-06-03 4:59 ` Nicholas Piggin
2021-05-21 9:41 ` [PATCH v4 15/16] crypto/nx: Get NX capabilities for GZIP coprocessor type Haren Myneni
2021-05-21 9:42 ` [PATCH v4 16/16] crypto/nx: Add sysfs interface to export NX capabilities Haren Myneni
2021-06-03 4:57 ` Nicholas Piggin
2021-06-04 1:02 ` Haren Myneni
2021-06-04 11:52 ` Michael Ellerman
2021-06-04 17:23 ` Haren Myneni
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=93586baca94d10ec5658d547b109aaa6a55ff635.camel@linux.ibm.com \
--to=haren@linux.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.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).