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 v2 6/6] s390/uv: Update query for secret-UVCs
Date: Mon, 5 Jun 2023 16:03:56 +0200 [thread overview]
Message-ID: <3eab8065-41e7-94b8-a6da-18222f711fa0@linux.ibm.com> (raw)
In-Reply-To: <20230519093708.810957-7-seiden@linux.ibm.com>
On 5/19/23 11:37, Steffen Eiden wrote:
> Update the query struct such that secret-UVC related
> information can be parsed.
> Add sysfs files for these new values.
>
> Signed-off-by: Steffen Eiden <seiden@linux.ibm.com>
You should add a bit of information about the fields.
Not a large amount but having no info doesn't help anyone without access
to our design documents.
> ---
[...]
> extern struct uv_info uv_info;
> diff --git a/arch/s390/kernel/uv.c b/arch/s390/kernel/uv.c
> index d5b5d7e83c17..c0a1bfb01135 100644
> --- a/arch/s390/kernel/uv.c
> +++ b/arch/s390/kernel/uv.c
> @@ -571,6 +571,42 @@ static ssize_t uv_query_supp_att_pflags(struct kobject *kobj,
> static struct kobj_attribute uv_query_supp_att_pflags_attr =
> __ATTR(supp_att_pflags, 0444, uv_query_supp_att_pflags, NULL);
>
> +static ssize_t uv_query_supp_add_secret_req_ver(struct kobject *kobj,
> + struct kobj_attribute *attr, char *page)
s/page/buf/ for the whole lot.
> +{
> + return sysfs_emit(page, "%lx\n", uv_info.supp_add_secret_req_ver);
> +}
> +
> +static struct kobj_attribute uv_query_supp_add_secret_req_ver_attr =
> + __ATTR(supp_add_secret_req_ver, 0444, uv_query_supp_add_secret_req_ver, NULL);
> +
> +static ssize_t uv_query_supp_add_secret_pcf(struct kobject *kobj,
> + struct kobj_attribute *attr, char *page)
> +{
> + return sysfs_emit(page, "%lx\n", uv_info.supp_add_secret_pcf);
> +}
> +
> +static struct kobj_attribute uv_query_supp_add_secret_pcf_attr =
> + __ATTR(supp_add_secret_pcf, 0444, uv_query_supp_add_secret_pcf, NULL);
> +
> +static ssize_t uv_query_supp_secret_types(struct kobject *kobj,
> + struct kobj_attribute *attr, char *page)
> +{
> + return sysfs_emit(page, "%lx\n", uv_info.supp_secret_types);
> +}
> +
> +static struct kobj_attribute uv_query_supp_secret_types_attr =
> + __ATTR(supp_secret_types, 0444, uv_query_supp_secret_types, NULL);
> +
> +static ssize_t uv_query_max_secrets(struct kobject *kobj,
> + struct kobj_attribute *attr, char *page)
> +{
> + return sysfs_emit(page, "%d\n", uv_info.max_secrets);
> +}
uv_query_max_secrets
but then
uv_query_max_num_secrets_attr
To num or not to num. That's the question
> +
> +static struct kobj_attribute uv_query_max_num_secrets_attr =
> + __ATTR(max_secrets, 0444, uv_query_max_secrets, NULL);
And here the num is gone again.
> +
> static struct attribute *uv_query_attrs[] = {
> &uv_query_facilities_attr.attr,
> &uv_query_feature_indications_attr.attr,
> @@ -584,6 +620,10 @@ static struct attribute *uv_query_attrs[] = {
> &uv_query_dump_cpu_len_attr.attr,
> &uv_query_supp_att_req_hdr_ver_attr.attr,
> &uv_query_supp_att_pflags_attr.attr,
> + &uv_query_supp_add_secret_req_ver_attr.attr,
> + &uv_query_supp_add_secret_pcf_attr.attr,
> + &uv_query_supp_secret_types_attr.attr,
> + &uv_query_max_num_secrets_attr.attr,
> NULL,
> };
>
prev parent reply other threads:[~2023-06-05 14:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 9:37 [PATCH v2 0/6] s390/uvdevice: Expose secret UVCs Steffen Eiden
2023-05-19 9:37 ` [PATCH v2 1/6] s390/uvdevice: Add info IOCTL Steffen Eiden
2023-06-05 12:39 ` Janosch Frank
2023-05-19 9:37 ` [PATCH v2 2/6] s390/uvdevice: Add 'Add Secret' UVC Steffen Eiden
2023-06-05 13:19 ` Janosch Frank
2023-05-19 9:37 ` [PATCH v2 3/6] s390/uvdevice: Add 'List Secrets' UVC Steffen Eiden
2023-06-05 13:29 ` Janosch Frank
2023-05-19 9:37 ` [PATCH v2 4/6] s390/uvdevice: Add 'Lock Secret Store' UVC Steffen Eiden
2023-06-05 13:34 ` Janosch Frank
2023-05-19 9:37 ` [PATCH v2 5/6] s390/uv: replace scnprintf with sysfs_emit Steffen Eiden
2023-06-05 13:55 ` Janosch Frank
2023-05-19 9:37 ` [PATCH v2 6/6] s390/uv: Update query for secret-UVCs Steffen Eiden
2023-06-05 14:03 ` 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=3eab8065-41e7-94b8-a6da-18222f711fa0@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