From: Cornelia Huck <cohuck@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
Janosch Frank <frankja@linux.vnet.ibm.com>
Cc: KVM <kvm@vger.kernel.org>,
Christian Borntraeger <borntraeger@de.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>
Subject: Re: [PATCH 0/2] KVM: s390: Enable some more facilities
Date: Tue, 22 Jun 2021 18:40:08 +0200 [thread overview]
Message-ID: <871r8tontj.fsf@redhat.com> (raw)
In-Reply-To: <20210622143412.143369-1-borntraeger@de.ibm.com>
On Tue, Jun 22 2021, Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> Some more facilities that can be enabled in the future.
>
> Christian Borntraeger (2):
> KVM: s390: gen_facilities: allow facilities 165, 193, 194 and 196
> KVM: s390: allow facility 192 (vector-packed-decimal-enhancement
> facility 2)
>
> arch/s390/kvm/kvm-s390.c | 4 ++++
> arch/s390/tools/gen_facilities.c | 4 ++++
> 2 files changed, 8 insertions(+)
I assume we can also expect some QEMU patches sometime in the future
that add some new features?
next prev parent reply other threads:[~2021-06-22 16:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 14:34 [PATCH 0/2] KVM: s390: Enable some more facilities Christian Borntraeger
2021-06-22 14:34 ` [PATCH 1/2] KVM: s390: gen_facilities: allow facilities 165, 193, 194 and 196 Christian Borntraeger
2021-06-22 16:24 ` Claudio Imbrenda
2021-06-22 16:38 ` Cornelia Huck
2021-06-23 7:29 ` Janosch Frank
2021-06-22 14:34 ` [PATCH 2/2] KVM: s390: allow facility 192 (vector-packed-decimal-enhancement facility 2) Christian Borntraeger
2021-06-22 16:28 ` Claudio Imbrenda
2021-06-22 16:39 ` Cornelia Huck
2021-06-23 7:30 ` Janosch Frank
2021-06-22 16:40 ` Cornelia Huck [this message]
2021-06-22 16:49 ` [PATCH 0/2] KVM: s390: Enable some more facilities Christian Borntraeger
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=871r8tontj.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.vnet.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@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;
as well as URLs for NNTP newsgroup(s).