In order to simplify the calling logic of uadk, a new init2 interface
is added to the cipher algorithm class, which includes hardware device
resource initialization and scheduler initialization.
Changes v2 -> v3:
Remove some redundant opcodes.
Changes v1 -> v2:
init2 interface and dynamic loading driver modification for splitting
Longfang Liu (2):
uadk/cipher: add the init2 interface for cipher
uadk/sec: adapt the sec module to the dynamic loading framework
drv/hisi_sec.c | 102 +++++++++++--
include/drv/wd_aead_drv.h | 2 +-
include/drv/wd_cipher_drv.h | 26 ----
include/drv/wd_digest_drv.h | 2 +-
include/wd_cipher.h | 29 ++++
libwd_crypto.map | 3 +
wd_cipher.c | 297 +++++++++++++++++++++++++++---------
7 files changed, 345 insertions(+), 116 deletions(-)
-------- Forwarded Message --------
Subject: S390 testing for IOMMUFD
Date: Mon, 7 Nov 2022 21:09:02 -0400
From: Jason Gunthorpe <jgg(a)nvidia.com>
To: Cornelia Huck <cohuck(a)redhat.com>, Eric Farman
<farman(a)linux.ibm.com>, Matthew Rosato <mjrosato(a)linux.ibm.com>, Niklas
Schnelle <schnelle(a)linux.ibm.com>, Tony Krowiak
<akrowiak(a)linux.ibm.com>, Halil Pasic <pasic(a)linux.ibm.com>, Jason Herne
CC: iommu(a)lists.linux.dev, Kevin Tian <kevin.tian(a)intel.com>, Alex
Williamson <alex.williamson(a)redhat.com>, kvm(a)vger.kernel.org, Lu Baolu
<baolu.lu(a)linux.intel.com>, Nicolin Chen <nicolinc(a)nvidia.com>
On Mon, Nov 07, 2022 at 08:48:53PM -0400, Jason Gunthorpe wrote:
> This has been in linux-next for a little while now, and we've completed
> the syzkaller run. 1300 hours of CPU time have been invested since the
> last report with no improvement in coverage or new detections. syzkaller
> coverage reached 69%(75%), and review of the misses show substantial
> amounts are WARN_ON's and other debugging which are not expected to be
> iommufd is the user API to control the IOMMU subsystem as it relates to
> managing IO page tables that point at user space memory.
[chop cc list]
s390 mdev maintainers,
Can I ask your help to test this with the two S390 mdev drivers? Now
that gvt is passing and we've covered alot of the QA ground it is a
good time to run it.
Take the branch from here:
And build the kernel with
And your existing stuff should work with iommufd providing the iommu
support to vfio. There will be a dmesg confirming this.
Let me know if there are any problems!
If I recall there was some desire from the S390 platform team to start
building on iommufd to create some vIOMMU acceleration for S390
guests, this is a necessary first step.