The commit applies fine to the noble master-next tree (kernel 6.8), and a test build was triggered here: https://launchpad.net/~fheimes/+archive/ubuntu/lp2074380
However, the cpumf code in jammy master-next (kernel 5.15) is quite different. git blame tells me that probably the following commits are needed as well: 111783-1a33aee1dc24 s390/cpum_cf: remove function validate_ctr_auth() by inline code 111784-9ae9b868aeaa s390/cpum_cf: provide counter number to validate_ctr_version() 111785:46c4d945ea1f s390/cpum_cf: introduce static CPU counter facility information but they (first of all 46c4d945ea1f) also do not apply cleanly. Would you please let us know a minimal set of patches (based on your insights of the code) that let us apply f10933cbd2df to the jammy master-next tree (git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy --branch master-next --single-branch) or alternatively a backport of f10933cbd2df to this tree? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2074380 Title: [UBUNTU 22.04] kernel: s390/cpum_cf: make crypto counters upward compatible Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: New Status in linux source package in Noble: New Bug description: Description: kernel: s390/cpum_cf: make crypto counters upward compatible Symptom: The CPU Measurement facility crypto counter set is not listed in the device sysfs tree. Problem: The CPU Measurement facility crypto counter set is not exported in the sysfs directory /sys/devices/cpum_cf/events. The attribute files for each CPU-MF counter defined in the crypto counter set is missing. This is caused by the counter second version number of the CPU Measurement Facility hardware being incremented on new machines. This causes a sanity check to fail, but the counters are supported by hardware. Solution: Remove upper limit in counter second version number check. Reproduction: Run command on a new machine generation: # ls -l /sys/devices/cpum_cf/events/ | grep AES # If the output is empty than this patch is required. The output should be: # ls /sys/devices/cpum_cf/events/ | grep AES AES_BLOCKED_CYCLES AES_BLOCKED_FUNCTIONS AES_CYCLES AES_FUNCTIONS # Upstream-ID of fix: f10933cbd2dfddf6273698a45f76db9bafd8150f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2074380/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
