From: Steffen Eiden <seiden@linux.ibm.com>
To: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
kvm@vger.kernel.org
Cc: Janosch Frank <frankja@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
David Hildenbrand <david@redhat.com>,
Michael Mueller <mimu@linux.vnet.ibm.com>,
Marc Hartmayer <mhartmay@linux.ibm.com>
Subject: [PATCH 0/3] KVM: s390: Enable AP instructions for pv-guests
Date: Thu, 27 Jul 2023 14:20:50 +0200 [thread overview]
Message-ID: <20230727122053.774473-1-seiden@linux.ibm.com> (raw)
This series enables general KVM support for AP pass-through for Secure
Execution guests (pv-guests).
To enable AP inside pv-guests two things have to be done/considered:
1) set corresponding flags in the Create Secure Configuration UVC ifi
firmware supports AP for pv-guests (patch 3).
2) enable/disable AP in pv-guests if the VMM wants this (patch 2).
Steffen
Steffen Eiden (3):
s390: uv: UV feature check utility
KVM: s390: Add UV feature negotiation
KVM: s390: pv: Allow AP-instructions for pv guests
arch/s390/include/asm/kvm_host.h | 2 +
arch/s390/include/asm/uv.h | 17 +++++++-
arch/s390/include/uapi/asm/kvm.h | 24 +++++++++++
arch/s390/kernel/uv.c | 2 +-
arch/s390/kvm/kvm-s390.c | 72 +++++++++++++++++++++++++++++++-
arch/s390/kvm/pv.c | 8 +++-
arch/s390/mm/fault.c | 2 +-
7 files changed, 121 insertions(+), 6 deletions(-)
--
2.40.1
next reply other threads:[~2023-07-27 12:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 12:20 Steffen Eiden [this message]
2023-07-27 12:20 ` [PATCH 1/3] s390: uv: UV feature check utility Steffen Eiden
2023-07-27 14:42 ` Claudio Imbrenda
2023-07-27 12:20 ` [PATCH 2/3] KVM: s390: Add UV feature negotiation Steffen Eiden
2023-07-27 15:02 ` Claudio Imbrenda
2023-07-27 12:20 ` [PATCH 3/3] KVM: s390: pv: Allow AP-instructions for pv guests Steffen Eiden
2023-07-27 15:07 ` 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=20230727122053.774473-1-seiden@linux.ibm.com \
--to=seiden@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@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=mhartmay@linux.ibm.com \
--cc=mimu@linux.vnet.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