Comment 7 for bug 1836153

@cborntra many thanks for the verification.

Commit 9967c2a is indeed not (yet) in this 4.15 bionic kernel.
It got upstream accepted with 4.20 and is with that in disco, hence that should all work on disco:

$ git log --oneline | grep -m 1 "s390/mm: fix mis-accounting of pgtable_bytes"
e12e404 s390/mm: fix mis-accounting of pgtable_bytes
$ git tag --contains e12e404
Ubuntu-5.0.0-7.8
...
Ubuntu-5.0.0-22.23
v5.0
$ rmadison --arch=s390x linux-generic | grep disco-proposed
 linux-generic | 5.0.0.22.23 | disco-proposed | s390x

Regarding bionic, the patch you pointed out will be picked up with the upstream stable release update process that is regularly done.
The next update is addressed by ticket LP 1836968 and covers patchset 2019-07-17, that includes "s390/mm: fix mis-accounting of pgtable_bytes"
(Ctrl+f on page https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836968 will show)
Hence there is no need to open a new LP for this particular patch or to submit it in a separate kernel SRU. Because it will probably come with the next bionic kernel update (since LP 1836968 is already marked as Fix Committed).

I think with strictly looking at the KVM part we can consider this verification as successfully done.

I will btw. mark the 'linux (Ubuntu)' entry that represents eoan and Fix Released, because with it's 5.2 kernel it has already everything need.