From: David Hildenbrand <david@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
Janosch Frank <frankja@linux.vnet.ibm.com>
Cc: KVM <kvm@vger.kernel.org>, Cornelia Huck <cohuck@redhat.com>,
Thomas Huth <thuth@redhat.com>,
Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
linux-s390 <linux-s390@vger.kernel.org>,
Michael Mueller <mimu@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>
Subject: Re: [PATCH v3 35/37] s390: protvirt: Add sysfs firmware interface for Ultravisor information
Date: Fri, 21 Feb 2020 11:46:47 +0100 [thread overview]
Message-ID: <4409e9ba-3b8c-69dd-815c-2b09d77d7598@redhat.com> (raw)
In-Reply-To: <20200220104020.5343-36-borntraeger@de.ibm.com>
On 20.02.20 11:40, Christian Borntraeger wrote:
> From: Janosch Frank <frankja@linux.ibm.com>
>
> That information, e.g. the maximum number of guests or installed
> Ultravisor facilities, is interesting for QEMU, Libvirt and
> administrators.
>
> Let's provide an easily parsable API to get that information.
>
> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
> ---
> arch/s390/kernel/uv.c | 86 +++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 86 insertions(+)
>
> diff --git a/arch/s390/kernel/uv.c b/arch/s390/kernel/uv.c
> index 4539003dac9d..550e9617c459 100644
> --- a/arch/s390/kernel/uv.c
> +++ b/arch/s390/kernel/uv.c
> @@ -323,5 +323,91 @@ int arch_make_page_accessible(struct page *page)
> return rc;
> }
> EXPORT_SYMBOL_GPL(arch_make_page_accessible);
> +#endif
> +
> +#if defined(CONFIG_PROTECTED_VIRTUALIZATION_GUEST) || IS_ENABLED(CONFIG_KVM)
> +static ssize_t uv_query_facilities(struct kobject *kobj,
> + struct kobj_attribute *attr, char *page)
> +{
> + return snprintf(page, PAGE_SIZE, "%lx\n%lx\n%lx\n%lx\n",
> + uv_info.inst_calls_list[0],
> + uv_info.inst_calls_list[1],
> + uv_info.inst_calls_list[2],
> + uv_info.inst_calls_list[3]);
> +}
> +
> +static struct kobj_attribute uv_query_facilities_attr =
> + __ATTR(facilities, 0444, uv_query_facilities, NULL);
> +
> +static ssize_t uv_query_max_guest_cpus(struct kobject *kobj,
> + struct kobj_attribute *attr, char *page)
> +{
> + return snprintf(page, PAGE_SIZE, "%d\n",
> + uv_info.max_guest_cpus);
> +}
> +
> +static struct kobj_attribute uv_query_max_guest_cpus_attr =
> + __ATTR(max_cpus, 0444, uv_query_max_guest_cpus, NULL);
> +
> +static ssize_t uv_query_max_guest_vms(struct kobject *kobj,
> + struct kobj_attribute *attr, char *page)
> +{
> + return snprintf(page, PAGE_SIZE, "%d\n",
> + uv_info.max_num_sec_conf);
> +}
> +
> +static struct kobj_attribute uv_query_max_guest_vms_attr =
> + __ATTR(max_guests, 0444, uv_query_max_guest_vms, NULL);
> +
> +static ssize_t uv_query_max_guest_addr(struct kobject *kobj,
> + struct kobj_attribute *attr, char *page)
> +{
> + return snprintf(page, PAGE_SIZE, "%lx\n",
> + uv_info.max_sec_stor_addr);
> +}
> +
> +static struct kobj_attribute uv_query_max_guest_addr_attr =
> + __ATTR(max_address, 0444, uv_query_max_guest_addr, NULL);
> +
> +static struct attribute *uv_query_attrs[] = {
> + &uv_query_facilities_attr.attr,
> + &uv_query_max_guest_cpus_attr.attr,
> + &uv_query_max_guest_vms_attr.attr,
> + &uv_query_max_guest_addr_attr.attr,
> + NULL,
> +};
> +
> +static struct attribute_group uv_query_attr_group = {
> + .attrs = uv_query_attrs,
> +};
>
> +static struct kset *uv_query_kset;
> +struct kobject *uv_kobj;
> +
> +static int __init uv_info_init(void)
> +{
> + int rc = -ENOMEM;
> +
> + if (!test_facility(158))
> + return 0;
> +
> + uv_kobj = kobject_create_and_add("uv", firmware_kobj);
> + if (!uv_kobj)
> + return -ENOMEM;
> +
> + uv_query_kset = kset_create_and_add("query", NULL, uv_kobj);
> + if (!uv_query_kset)
> + goto out_kobj;
> +
> + rc = sysfs_create_group(&uv_query_kset->kobj, &uv_query_attr_group);
> + if (!rc)
> + return 0;
> +
> + kset_unregister(uv_query_kset);
> +out_kobj:
> + kobject_del(uv_kobj);
> + kobject_put(uv_kobj);
> + return rc;
> +}
> +device_initcall(uv_info_init);
> #endif
>
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2020-02-21 10:46 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 10:39 [PATCH v3 00/37] KVM: s390: Add support for protected VMs Christian Borntraeger
2020-02-20 10:39 ` [PATCH v3 01/37] mm:gup/writeback: add callbacks for inaccessible pages Christian Borntraeger
2020-02-20 12:15 ` David Hildenbrand
2020-02-20 10:39 ` [PATCH v3 02/37] KVM: s390/interrupt: do not pin adapter interrupt pages Christian Borntraeger
2020-02-21 8:09 ` [PATCH v3.1 " Christian Borntraeger
2020-02-21 9:50 ` David Hildenbrand
2020-02-21 10:41 ` Cornelia Huck
2020-02-21 11:05 ` Christian Borntraeger
2020-02-20 10:39 ` [PATCH v3 03/37] s390/protvirt: introduce host side setup Christian Borntraeger
2020-02-21 12:39 ` Cornelia Huck
2020-02-20 10:39 ` [PATCH v3 04/37] s390/protvirt: add ultravisor initialization Christian Borntraeger
2020-02-20 10:39 ` [PATCH v3 05/37] s390/mm: provide memory management functions for protected KVM guests Christian Borntraeger
2020-02-20 12:25 ` David Hildenbrand
2020-02-20 10:39 ` [PATCH v3 06/37] s390/mm: add (non)secure page access exceptions handlers Christian Borntraeger
2020-02-21 10:38 ` David Hildenbrand
2020-02-20 10:39 ` [PATCH v3 07/37] KVM: s390: protvirt: Add UV debug trace Christian Borntraeger
2020-02-20 10:39 ` [PATCH v3 08/37] KVM: s390: add new variants of UV CALL Christian Borntraeger
2020-02-20 10:39 ` [PATCH v3 09/37] KVM: s390: protvirt: Add initial vm and cpu lifecycle handling Christian Borntraeger
2020-02-20 13:02 ` David Hildenbrand
2020-02-20 19:44 ` Christian Borntraeger
2020-02-21 8:07 ` [PATCH v3.1 " Christian Borntraeger
2020-02-21 11:45 ` David Hildenbrand
2020-02-21 13:03 ` Christian Borntraeger
2020-02-21 13:08 ` David Hildenbrand
2020-02-21 8:22 ` [PATCH v3 " David Hildenbrand
2020-02-21 8:40 ` Christian Borntraeger
2020-02-21 11:47 ` David Hildenbrand
2020-02-20 10:39 ` [PATCH v3 10/37] KVM: s390: protvirt: Add KVM api documentation Christian Borntraeger
2020-02-20 13:05 ` David Hildenbrand
2020-02-20 13:55 ` Christian Borntraeger
2020-02-20 10:39 ` [PATCH v3 11/37] KVM: s390: protvirt: Secure memory is not mergeable Christian Borntraeger
2020-02-21 12:49 ` Cornelia Huck
2020-02-20 10:39 ` [PATCH v3 12/37] KVM: s390/mm: Make pages accessible before destroying the guest Christian Borntraeger
2020-02-20 10:39 ` [PATCH v3 13/37] KVM: s390: protvirt: Handle SE notification interceptions Christian Borntraeger
2020-02-20 10:39 ` [PATCH v3 14/37] KVM: s390: protvirt: Instruction emulation Christian Borntraeger
2020-02-20 10:39 ` [PATCH v3 15/37] KVM: s390: protvirt: Implement interrupt injection Christian Borntraeger
2020-02-20 10:39 ` [PATCH v3 16/37] KVM: s390: protvirt: Add SCLP interrupt handling Christian Borntraeger
2020-02-20 10:40 ` [PATCH v3 17/37] KVM: s390: protvirt: Handle spec exception loops Christian Borntraeger
2020-02-20 10:40 ` [PATCH v3 18/37] KVM: s390: protvirt: Add new gprs location handling Christian Borntraeger
2020-02-20 10:40 ` [PATCH v3 19/37] KVM: S390: protvirt: Introduce instruction data area bounce buffer Christian Borntraeger
2020-02-20 10:40 ` [PATCH v3 20/37] KVM: s390: protvirt: handle secure guest prefix pages Christian Borntraeger
2020-02-20 10:40 ` [PATCH v3 21/37] KVM: s390/mm: handle guest unpin events Christian Borntraeger
2020-02-20 10:40 ` [PATCH v3 22/37] KVM: s390: protvirt: Write sthyi data to instruction data area Christian Borntraeger
2020-02-20 10:40 ` [PATCH v3 23/37] KVM: s390: protvirt: STSI handling Christian Borntraeger
2020-02-20 10:40 ` [PATCH v3 24/37] KVM: s390: protvirt: disallow one_reg Christian Borntraeger
2020-02-20 10:40 ` [PATCH v3 25/37] KVM: s390: protvirt: Do only reset registers that are accessible Christian Borntraeger
2020-02-21 10:39 ` David Hildenbrand
2020-02-20 10:40 ` [PATCH v3 26/37] KVM: s390: protvirt: Only sync fmt4 registers Christian Borntraeger
2020-02-21 10:43 ` David Hildenbrand
2020-02-20 10:40 ` [PATCH v3 27/37] KVM: s390: protvirt: Add program exception injection Christian Borntraeger
2020-02-20 10:40 ` [PATCH v3 28/37] KVM: s390: protvirt: UV calls in support of diag308 0, 1 Christian Borntraeger
2020-02-21 10:44 ` David Hildenbrand
2020-02-20 10:40 ` [PATCH v3 29/37] KVM: s390: protvirt: Report CPU state to Ultravisor Christian Borntraeger
2020-02-20 10:40 ` [PATCH v3 30/37] KVM: s390: protvirt: Support cmd 5 operation state Christian Borntraeger
2020-02-20 10:40 ` [PATCH v3 31/37] KVM: s390: protvirt: Mask PSW interrupt bits for interception 104 and 112 Christian Borntraeger
2020-02-20 10:40 ` [PATCH v3 32/37] KVM: s390: protvirt: do not inject interrupts after start Christian Borntraeger
2020-02-20 10:40 ` [PATCH v3 33/37] KVM: s390: protvirt: Add UV cpu reset calls Christian Borntraeger
2020-02-20 10:40 ` [PATCH v3 34/37] DOCUMENTATION: Protected virtual machine introduction and IPL Christian Borntraeger
2020-02-20 10:40 ` [PATCH v3 35/37] s390: protvirt: Add sysfs firmware interface for Ultravisor information Christian Borntraeger
2020-02-21 10:46 ` David Hildenbrand [this message]
2020-02-20 10:40 ` [PATCH v3 36/37] KVM: s390: rstify new ioctls in api.rst Christian Borntraeger
2020-02-21 10:47 ` David Hildenbrand
2020-02-21 10:51 ` Cornelia Huck
2020-02-21 11:13 ` Christian Borntraeger
2020-02-20 10:40 ` [PATCH v3 37/37] KVM: s390: protvirt: introduce and enable KVM_CAP_S390_PROTECTED Christian Borntraeger
2020-02-21 10:47 ` David Hildenbrand
2020-02-21 10:54 ` [PATCH v3 00/37] KVM: s390: Add support for protected VMs David Hildenbrand
2020-02-21 11:26 ` Christian Borntraeger
2020-02-21 11:28 ` David Hildenbrand
2020-02-21 13:45 ` Cornelia Huck
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=4409e9ba-3b8c-69dd-815c-2b09d77d7598@redhat.com \
--to=david@redhat.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=frankja@linux.vnet.ibm.com \
--cc=gor@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mimu@linux.ibm.com \
--cc=thuth@redhat.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