Comment 34 for bug 1787405

------- Comment From <email address hidden> 2018-11-07 10:16 EDT-------
I installed a fresh Ubuntu 18.04.1 on a LPAR and after booting
these both packages on top:

linux-image-4.15.0-38-generic_4.15.0-38.42~lp1787405_s390x.deb
linux-modules-4.15.0-38-generic_4.15.0-38.42~lp1787405_s390x.deb

then I needed to configure zipl to something usefull as the modified zipl.conf obviously is somewhat broken after package install:

--------------------------------------------------------------------------------
[defaultboot]
defaultmenu=menu

[UBUNTU18.04.1]
target=/boot
image=/boot/vmlinuz.old
parameters="scsi_mod.scsi_logging_level=4605 printk.time=1 zfcp.dbfsize=100 root=/dev/disk/by-path/ccw-0.0.e96b-part1"
ramdisk=/boot/initrd.img.old

[newkernel]
target=/boot
image=/boot/vmlinuz
parameters="scsi_mod.scsi_logging_level=4605 printk.time=1 zfcp.dbfsize=100 root=/dev/disk/by-path/ccw-0.0.e96b-part1"
ramdisk=/boot/initrd.img

:menu
target=/boot
1 = UBUNTU18.04.1
2 = newkernel
default = 2
prompt = 1
timeout = 10

--------------------------------------------------------------------------------

after boot the new kernel is active:

uname -a
Linux s83lp75 4.15.0-38-generic #42~lp1787405 SMP Mon Nov 5 21:13:01 UTC 2018 s390x s390x s390x GNU/Linux

then I ran my brand new developed zcrypttest and all the testcases ran fine.
This is at least an indication that the zcrypt dd is not broken, multi domain and multi adapter works and all the 3 kinds of adapters can get addressed with all the different cprbs and work as expected. Even more some basic assumptions about request scheduling memory consumptions are tested.

What's not covered is the new functionallity coming with the apmask and aqmask. I'll do this later as I'd like to devel some testcases for this feature in the next days.