From: Pierre Morel <pmorel@linux.ibm.com>
To: kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
borntraeger@de.ibm.com, frankja@linux.ibm.com, cohuck@redhat.com,
david@redhat.com, thuth@redhat.com, imbrenda@linux.ibm.com,
hca@linux.ibm.com, gor@linux.ibm.com, pmorel@linux.ibm.com
Subject: [PATCH v1 2/2] KVM: s390: Topology expose TOPOLOGY facility
Date: Wed, 14 Jul 2021 17:25:43 +0200 [thread overview]
Message-ID: <1626276343-22805-3-git-send-email-pmorel@linux.ibm.com> (raw)
In-Reply-To: <1626276343-22805-1-git-send-email-pmorel@linux.ibm.com>
We add the KVM extension KVM_CAP_S390_CPU_TOPOLOGY, this will
allow the userland hypervisor to handle the interception of the
PTF (Perform topology Function) instruction.
Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
---
arch/s390/tools/gen_facilities.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/s390/tools/gen_facilities.c b/arch/s390/tools/gen_facilities.c
index 606324e56e4e..2c260eb22bae 100644
--- a/arch/s390/tools/gen_facilities.c
+++ b/arch/s390/tools/gen_facilities.c
@@ -112,6 +112,7 @@ static struct facility_def facility_defs[] = {
.name = "FACILITIES_KVM_CPUMODEL",
.bits = (int[]){
+ 11, /* configuration topology facility */
12, /* AP Query Configuration Information */
15, /* AP Facilities Test */
156, /* etoken facility */
--
2.25.1
next prev parent reply other threads:[~2021-07-14 15:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 15:25 [PATCH v1 0/2] s390x: KVM: CPU Topology Pierre Morel
2021-07-14 15:25 ` [PATCH v1 1/2] s390x: KVM: accept STSI for CPU topology information Pierre Morel
2021-07-15 8:51 ` David Hildenbrand
2021-07-15 9:30 ` Cornelia Huck
2021-07-15 10:01 ` David Hildenbrand
2021-07-15 10:16 ` Cornelia Huck
2021-07-15 10:19 ` David Hildenbrand
2021-07-15 11:37 ` Pierre Morel
2021-07-15 11:31 ` Pierre Morel
2021-07-15 11:31 ` Pierre Morel
2021-07-14 15:25 ` Pierre Morel [this message]
2021-07-15 8:52 ` [PATCH v1 2/2] KVM: s390: Topology expose TOPOLOGY facility David Hildenbrand
2021-07-15 10:48 ` Pierre Morel
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=1626276343-22805-3-git-send-email-pmorel@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=gor@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=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