From: "Jason J. Herne" <jjherne@linux.ibm.com>
To: linux-s390@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, pasic@linux.ibm.com,
akrowiak@linux.ibm.com
Subject: [PATCH 0/3] s390/vfio-ap: queue_configuration sysfs attribute for mdevctl automation
Date: Fri, 26 Jan 2024 09:35:30 -0500 [thread overview]
Message-ID: <20240126143533.14043-1-jjherne@linux.ibm.com> (raw)
Mdevctl requires a way to atomically query and atomically update a vfio-ap
mdev's current state. This patch set creates the queue_configuration sysfs
attribute. This new attribute allows reading and writing an mdev's entire
state in one go. If a newly written state is invalid for any reason the entire
state is rejected and the target mdev remains unchanged.
Jason J. Herne (3):
s390/ap: Externalize AP bus specific bitmap reading function
s390/vfio-ap: Add sysfs attr, queue_configuration, to export mdev
state
s390/vfio-ap: Add write support to sysfs attr ap_config
Documentation/arch/s390/vfio-ap.rst | 27 ++++
drivers/s390/crypto/ap_bus.c | 13 +-
drivers/s390/crypto/ap_bus.h | 22 +++
drivers/s390/crypto/vfio_ap_ops.c | 213 +++++++++++++++++++++++---
drivers/s390/crypto/vfio_ap_private.h | 6 +-
5 files changed, 248 insertions(+), 33 deletions(-)
--
2.41.0
next reply other threads:[~2024-01-26 14:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 14:35 Jason J. Herne [this message]
2024-01-26 14:35 ` [PATCH 1/3] s390/ap: Externalize AP bus specific bitmap reading function Jason J. Herne
2024-01-26 14:35 ` [PATCH 2/3] s390/vfio-ap: Add sysfs attr, queue_configuration, to export mdev state Jason J. Herne
2024-01-29 15:30 ` Anthony Krowiak
2024-01-26 14:35 ` [PATCH 3/3] s390/vfio-ap: Add write support to sysfs attr ap_config Jason J. Herne
2024-01-28 14:02 ` kernel test robot
2024-01-29 21:43 ` Anthony Krowiak
2024-03-05 20:41 ` Jason J. Herne
2024-01-29 16:53 ` [PATCH 0/3] s390/vfio-ap: queue_configuration sysfs attribute for mdevctl automation Anthony Krowiak
2024-01-29 20:23 ` Matthew Rosato
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=20240126143533.14043-1-jjherne@linux.ibm.com \
--to=jjherne@linux.ibm.com \
--cc=akrowiak@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@linux.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