From: Christian Borntraeger <borntraeger@linux.ibm.com>
To: KVM <kvm@vger.kernel.org>
Cc: Janosch Frank <frankja@linux.ibm.com>,
David Hildenbrand <david@redhat.com>,
linux-s390 <linux-s390@vger.kernel.org>,
Thomas Huth <thuth@redhat.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Janis Schoetterl-Glausch <scgl@linux.ibm.com>
Subject: Re: [PATCH 1/1] KVM: s390: Add facility 197 to the white list
Date: Mon, 11 Jul 2022 15:11:30 +0200 [thread overview]
Message-ID: <754d4ea2-8a1a-9b09-50c1-f877696b81f2@linux.ibm.com> (raw)
In-Reply-To: <20220711115108.6494-1-borntraeger@linux.ibm.com>
Am 11.07.22 um 13:51 schrieb Christian Borntraeger:
> z16 also provides facility 197 (The processor-activity-instrumentation
> extension 1). Lets add it to KVM.
>
> Signed-off-by: Christian Borntraeger <borntraeger@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 530dd941d140..cb0aff5c0187 100644
> --- a/arch/s390/tools/gen_facilities.c
> +++ b/arch/s390/tools/gen_facilities.c
> @@ -111,6 +111,7 @@ static struct facility_def facility_defs[] = {
> 193, /* bear enhancement facility */
> 194, /* rdp enhancement facility */
> 196, /* processor activity instrumentation facility */
> + 197, /* processor activity instrumentation extension 1 */
> -1 /* END */
> }
> },
Unless there are complaints, I will queue this with "white list" -> "allow list" and "lets" -> "let's".
next prev parent reply other threads:[~2022-07-11 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 11:51 [PATCH 1/1] KVM: s390: Add facility 197 to the white list Christian Borntraeger
2022-07-11 13:11 ` Christian Borntraeger [this message]
2022-07-11 13:14 ` Thomas Huth
2022-07-11 13:25 ` Claudio Imbrenda
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=754d4ea2-8a1a-9b09-50c1-f877696b81f2@linux.ibm.com \
--to=borntraeger@linux.ibm.com \
--cc=agordeev@linux.ibm.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-s390@vger.kernel.org \
--cc=scgl@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