** Description changed:
+ [Impact]
+
+ * HW enablement
+ * Kernel supports alternate zcrypt device drivers, hence lszcrypt (an
information tool) should show if a driver is bound, and which one, given that
it is no longer unambiguous.
+
+ [Test Case]
+
+ * Run lszcrypt, ensure it shows info about crypto cards, and a driver
+ name.
+
+ [Regression Potential]
+
+ * Changes are to an informational lszcrypt tool, output of which is now
+ chnaged, but is not typically parsed in an automated fashion.
+ (automation is usually done with lszdev/chzdev commands)
+
+ [Other Info]
+
+ * Original bug report:
+
With the introduction of KVM crypto virtualization the driver bound to an AP
queue device is no longer unique determined.
This feature provides a deterministic hot plugging semantics of AP queues
that may be bound to multiple drivers.
In particular it enables to configure an AP queue (APQN) as being bound to a
particular driver even if the associate HW gets intermittently lost and
reconnected.
s390-tools part.
Backport from 2.7.0 to 2.6.0
Git commit: for s390-tools 2.7.0
https://github.com/ibm-s390-tools/s390-tools/commit/0a0b4c382693cded5652404e8fa2c0e483aa33df
lszcrypt: support for alternate zcrypt device drivers
It needs to be applied to 2.6.0 for Ubuntu 18.10, which will apply
seamlessly
** Changed in: s390-tools (Ubuntu Cosmic)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800867
Title:
[18.10 FEAT] zcrypt DD: introduce APQN tags to support deterministic
driver binding - s390tools part
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1800867/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
