From: Janosch Frank <frankja@linux.ibm.com>
To: Steffen Eiden <seiden@linux.ibm.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org,
Viktor Mihajlovski <mihajlov@linux.ibm.com>
Cc: Claudio Imbrenda <imbrenda@linux.ibm.com>,
Nico Boehr <nrb@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Hendrik Brueckner <brueckner@linux.ibm.com>
Subject: Re: [PATCH v4 6/6] s390/uv: Update query for secret-UVCs
Date: Wed, 7 Jun 2023 14:32:50 +0200 [thread overview]
Message-ID: <e2b8d63e-06ff-bbd7-b76d-e358a9a8533e@linux.ibm.com> (raw)
In-Reply-To: <20230606180817.3019077-7-seiden@linux.ibm.com>
On 6/6/23 20:08, Steffen Eiden wrote:
> Update the query struct such that secret-UVC related
> information can be parsed.
> Add sysfs files for these new values.
>
> 'supp_add_secret_req_ver' notes the supported versions for the
> Add Secret UVC. Bit 0 indicates that version 0x100 is supported,
> bit 1 indicates 0x200, and so on.
>
> 'supp_add_secret_pcf' notes the supported plaintext flags for
> the Add Secret UVC.
>
> 'supp_secret_types' notes the supported types of secrets.
> Bit 0 indicates secret type 1, bit 1 indicates type 2, and so on.
>
> 'max_secrets' notes the maximum amount of secrets the secret store can
> store per pv guest.
>
> Signed-off-by: Steffen Eiden <seiden@linux.ibm.com>
> ---
> arch/s390/boot/uv.c | 4 ++++
> arch/s390/include/asm/uv.h | 13 +++++++++++--
> arch/s390/kernel/uv.c | 40 ++++++++++++++++++++++++++++++++++++++
> 3 files changed, 55 insertions(+), 2 deletions(-)
>
> diff --git a/arch/s390/boot/uv.c b/arch/s390/boot/uv.c
> index 0a077c0a2056..cdffc395f1cd 100644
> --- a/arch/s390/boot/uv.c
> +++ b/arch/s390/boot/uv.c
> @@ -47,6 +47,10 @@ void uv_query_info(void)
> uv_info.conf_dump_finalize_len = uvcb.conf_dump_finalize_len;
> uv_info.supp_att_req_hdr_ver = uvcb.supp_att_req_hdr_ver;
> uv_info.supp_att_pflags = uvcb.supp_att_pflags;
> + uv_info.supp_add_secret_req_ver = uvcb.supp_add_secret_req_ver;
> + uv_info.supp_add_secret_pcf = uvcb.supp_add_secret_pcf;
> + uv_info.supp_secret_types = uvcb.supp_secret_types;
> + uv_info.max_secrets = uvcb.max_secrets
Apart from this:
Reviewed-by: Janosch Frank <frankja@linux.ibm.com>
But we can add the ";" when picking.
prev parent reply other threads:[~2023-06-07 12:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 18:08 [PATCH v4 0/6] s390/uvdevice: Expose secret UVCs Steffen Eiden
2023-06-06 18:08 ` [PATCH v4 1/6] s390/uvdevice: Add info IOCTL Steffen Eiden
2023-06-06 18:08 ` [PATCH v4 2/6] s390/uvdevice: Add 'Add Secret' UVC Steffen Eiden
2023-06-07 12:15 ` Janosch Frank
2023-06-06 18:08 ` [PATCH v4 3/6] s390/uvdevice: Add 'List Secrets' UVC Steffen Eiden
2023-06-07 12:21 ` Janosch Frank
2023-06-06 18:08 ` [PATCH v4 4/6] s390/uvdevice: Add 'Lock Secret Store' UVC Steffen Eiden
2023-06-07 12:24 ` Janosch Frank
2023-06-06 18:08 ` [PATCH v4 5/6] s390/uv: replace scnprintf with sysfs_emit Steffen Eiden
2023-06-07 12:28 ` Janosch Frank
2023-06-06 18:08 ` [PATCH v4 6/6] s390/uv: Update query for secret-UVCs Steffen Eiden
2023-06-07 6:43 ` kernel test robot
2023-06-07 12:32 ` Janosch Frank [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=e2b8d63e-06ff-bbd7-b76d-e358a9a8533e@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=brueckner@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mihajlov@linux.ibm.com \
--cc=nrb@linux.ibm.com \
--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