From: Janosch Frank <frankja@linux.ibm.com>
To: kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, imbrenda@linux.ibm.com,
thuth@redhat.com, david@redhat.com, nsg@linux.ibm.com,
nrb@linux.ibm.com, akrowiak@linux.ibm.com, jjherne@linux.ibm.com
Subject: [kvm-unit-tests PATCH v4 0/7] s390x: Add base AP support
Date: Fri, 2 Feb 2024 14:59:06 +0000 [thread overview]
Message-ID: <20240202145913.34831-1-frankja@linux.ibm.com> (raw)
As KVM supports passing Adjunct Processor (AP) crypto devices to
guests, we should make sure that the interface works as expected.
Three instructions provide the interface to the AP devices:
- nqap: Enqueues a crypto request
- dqap: Dequeues a crypto request
- pqap: Provides information and processes support functions
nqap & dqap work on crypto requests for which we currently don't want
to add tests due to their sheer complexity.
Which leaves us with pqap which is partly emulated for a guest 2 and
hence is a prime target for testing.
v4:
- Rebase on the cc dirty series
- Bumped year to 2024
v3:
- Renamed ap_check() to ap_setup() and added comment
v2:
- Re-worked the ap_check() function to test for stfle 12 since
we rely on PQAP QCI in the library functions
- Re-worked APQN management
- Fixed faulty loop variable initializers in ap.c
- Fixed report messages
- Extended clobber lists
- Extended length bit checks for nqap
- Now using ARRAY_SIZE where applicabale
- NIB is now allocated as IO memory
Janosch Frank (7):
lib: s390x: Add ap library
s390x: Add guest 2 AP test
lib: s390x: ap: Add proper ap setup code
s390x: ap: Add pqap aqic tests
s390x: ap: Add reset tests
lib: s390x: ap: Add tapq test facility bit
s390x: ap: Add nq/dq len test
lib/s390x/ap.c | 286 ++++++++++++++++++++++
lib/s390x/ap.h | 119 ++++++++++
s390x/Makefile | 2 +
s390x/ap.c | 564 ++++++++++++++++++++++++++++++++++++++++++++
s390x/unittests.cfg | 3 +
5 files changed, 974 insertions(+)
create mode 100644 lib/s390x/ap.c
create mode 100644 lib/s390x/ap.h
create mode 100644 s390x/ap.c
--
2.40.1
next reply other threads:[~2024-02-02 15:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 14:59 Janosch Frank [this message]
2024-02-02 14:59 ` [kvm-unit-tests PATCH v4 1/7] lib: s390x: Add ap library Janosch Frank
2024-02-05 18:15 ` Anthony Krowiak
2024-02-06 8:48 ` Harald Freudenberger
2024-02-06 15:45 ` Anthony Krowiak
2024-02-06 13:42 ` Janosch Frank
2024-02-06 15:55 ` Anthony Krowiak
2024-02-07 8:06 ` Harald Freudenberger
2024-02-07 14:30 ` Anthony Krowiak
2024-02-02 14:59 ` [kvm-unit-tests PATCH v4 2/7] s390x: Add guest 2 AP test Janosch Frank
2024-02-20 16:38 ` Anthony Krowiak
2024-02-21 7:57 ` Janosch Frank
2024-02-02 14:59 ` [kvm-unit-tests PATCH v4 3/7] lib: s390x: ap: Add proper ap setup code Janosch Frank
2024-02-02 14:59 ` [kvm-unit-tests PATCH v4 4/7] s390x: ap: Add pqap aqic tests Janosch Frank
2024-02-02 14:59 ` [kvm-unit-tests PATCH v4 5/7] s390x: ap: Add reset tests Janosch Frank
2024-02-02 14:59 ` [kvm-unit-tests PATCH v4 6/7] lib: s390x: ap: Add tapq test facility bit Janosch Frank
2024-02-02 14:59 ` [kvm-unit-tests PATCH v4 7/7] s390x: ap: Add nq/dq len test Janosch Frank
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=20240202145913.34831-1-frankja@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=akrowiak@linux.ibm.com \
--cc=david@redhat.com \
--cc=imbrenda@linux.ibm.com \
--cc=jjherne@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=nsg@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