From: Tony Krowiak <akrowiak@linux.ibm.com>
To: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: borntraeger@de.ibm.com, cohuck@redhat.com,
pasic@linux.vnet.ibm.com, jjherne@linux.ibm.com, jgg@nvidia.com,
alex.williamson@redhat.com, kwankhede@nvidia.com,
frankja@linux.ibm.com, david@redhat.com, imbrenda@linux.ibm.com,
hca@linux.ibm.com
Subject: [PATCH v2 0/2] s390/vfio-ap: do not open code locks for
Date: Mon, 23 Aug 2021 17:20:45 -0400 [thread overview]
Message-ID: <20210823212047.1476436-1-akrowiak@linux.ibm.com> (raw)
The subject line does not necessarily encompass both patches of this
two-patch series, but I left it as versions 1 and 2 used this subject
line and I didn't want to confuse those who reviewed those patches.
Change log v1->v2:
-----------------
* Both of these patches were rebased on Alex's linux-vfio-next tree taken
from https://github.com/awilliam/linux-vfio.git.
* Replaced kvm_s390_module_hook structure with a function pointer to the
interception handler for the PQAP(AQIC) instruction.
Tony Krowiak (2):
s390/vfio-ap: r/w lock for PQAP interception handler function pointer
s390/vfio-ap: replace open coded locks for VFIO_GROUP_NOTIFY_SET_KVM
notification
arch/s390/include/asm/kvm_host.h | 8 +-
arch/s390/kvm/kvm-s390.c | 32 ++++++-
arch/s390/kvm/priv.c | 15 +--
drivers/s390/crypto/vfio_ap_ops.c | 127 +++++++++-----------------
drivers/s390/crypto/vfio_ap_private.h | 4 +-
5 files changed, 84 insertions(+), 102 deletions(-)
--
2.31.1
next reply other threads:[~2021-08-23 21:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 21:20 Tony Krowiak [this message]
2021-08-23 21:20 ` [PATCH v2 1/2] s390/vfio-ap: r/w lock for PQAP interception handler function pointer Tony Krowiak
2021-08-23 21:20 ` [PATCH v2 2/2] s390/vfio-ap: replace open coded locks for VFIO_GROUP_NOTIFY_SET_KVM notification Tony Krowiak
2021-08-26 22:20 ` [PATCH v2 0/2] s390/vfio-ap: do not open code locks for Alex Williamson
2021-08-27 13:43 ` Tony Krowiak
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=20210823212047.1476436-1-akrowiak@linux.ibm.com \
--to=akrowiak@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=jgg@nvidia.com \
--cc=jjherne@linux.ibm.com \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@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
all inboxes | Powered by JetHome®