From: "Christoph Schlameuss" <schlameuss@linux.ibm.com>
To: "Steffen Eiden" <seiden@linux.ibm.com>,
<linux-kernel@vger.kernel.org>, <linux-s390@vger.kernel.org>
Cc: "Ingo Franzki" <ifranzki@linux.ibm.com>,
"Harald Freudenberger" <freude@linux.ibm.com>,
"Janosch Frank" <frankja@linux.ibm.com>,
"Claudio Imbrenda" <imbrenda@linux.ibm.com>
Subject: Re: [PATCH v1 6/6] s390/uv: Retrieve UV secrets sysfs support
Date: Tue, 01 Oct 2024 19:42:11 +0200 [thread overview]
Message-ID: <D4KNL7YPNFYD.2FD1QX5DFT8H8@linux.ibm.com> (raw)
In-Reply-To: <20240930131909.2079965-7-seiden@linux.ibm.com>
On Mon Sep 30, 2024 at 3:19 PM CEST, Steffen Eiden wrote:
> Reflect the updated content in the query information UVC to the sysfs at
> /sys/firmware/query
>
> * new UV-query sysfs entry for the maximum number of retrievable
> secrets the UV can store for one secure guest.
> * new UV-query sysfs entry for the maximum number of association
> secrets the UV can store for one secure guest.
> * max_secrets contains the sum of max association and max retrievable
> secrets.
>
> Signed-off-by: Steffen Eiden <seiden@linux.ibm.com>
Reviewed-by: Christoph Schlameuss <schlameuss@linux.ibm.com>
> ---
> arch/s390/boot/uv.c | 3 ++-
> arch/s390/include/asm/uv.h | 8 +++++---
> arch/s390/kernel/uv.c | 24 +++++++++++++++++++++++-
> 3 files changed, 30 insertions(+), 5 deletions(-)
[...]
> diff --git a/arch/s390/include/asm/uv.h b/arch/s390/include/asm/uv.h
> index 6838aa23e4e5..91631bea22d8 100644
> --- a/arch/s390/include/asm/uv.h
> +++ b/arch/s390/include/asm/uv.h
> @@ -144,8 +144,9 @@ struct uv_cb_qui {
> u64 supp_add_secret_req_ver; /* 0x00f8 */
> u64 supp_add_secret_pcf; /* 0x0100 */
> u64 supp_secret_types; /* 0x0180 */
This is not part of your patch, but maybe you can correct this with this
adjacent edit.
supp_secret_types is located at 0x0108.
> - u16 max_secrets; /* 0x0110 */
> - u8 reserved112[0x120 - 0x112]; /* 0x0112 */
> + u16 max_assoc_secrets; /* 0x0110 */
> + u16 max_retr_secrets; /* 0x0112 */
> + u8 reserved114[0x120 - 0x114]; /* 0x0114 */
> } __packed __aligned(8);
[...]
prev parent reply other threads:[~2024-10-01 17:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 13:19 [PATCH v1 0/6] s390/uv: Retrieve Secrets Ultravisor Call support Steffen Eiden
2024-09-30 13:19 ` [PATCH v1 1/6] s390/boot/uv.c: Use a constant for more-data rc Steffen Eiden
2024-10-01 12:10 ` Claudio Imbrenda
2024-10-01 13:56 ` Janosch Frank
2024-09-30 13:19 ` [PATCH v1 2/6] s390/uv: Retrieve UV secrets support Steffen Eiden
2024-10-01 16:06 ` Christoph Schlameuss
2024-10-02 7:51 ` Janosch Frank
2024-09-30 13:19 ` [PATCH v1 3/6] s390/uvdevice: Add Retrieve Secret IOCTL Steffen Eiden
2024-10-01 16:09 ` Christoph Schlameuss
2024-09-30 13:19 ` [PATCH v1 4/6] s390/uvdevice: Increase indent in IOCTL definitions Steffen Eiden
2024-09-30 13:19 ` [PATCH v1 5/6] s390/uvdevice: Add List Secrets Ext IOCTL Steffen Eiden
2024-10-01 16:19 ` Christoph Schlameuss
2024-09-30 13:19 ` [PATCH v1 6/6] s390/uv: Retrieve UV secrets sysfs support Steffen Eiden
2024-10-01 17:42 ` Christoph Schlameuss [this message]
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=D4KNL7YPNFYD.2FD1QX5DFT8H8@linux.ibm.com \
--to=schlameuss@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=ifranzki@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=seiden@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