* I know, one could as well call that a "feature", but it really is a
performance bug fix more than anything else. Also the SRU policy allows
exploitation/toleration of new HW especially for LTS releases.
Therefore I think this is fine as SRU.
I'm okay with that interpretation also. My doubt is about allowing userspace to map the MSI-X table, which is not currently allowed.
Actually ... it would be allowed and it would have an "undefined behavior" because of the sparse feature. So, perhaps you're right and it could be seen as a fix both ways: fixing undefined behavior and allowing the MSI-X table to be mmaped, which will allow better performance for QEMU.
After re-thinking, I'm +1 on the backport for Bionic Kernel also if others agree.
After reading this:
* I know, one could as well call that a "feature", but it really is a /toleration of new HW especially for LTS releases.
performance bug fix more than anything else. Also the SRU policy allows
exploitation
Therefore I think this is fine as SRU.
I'm okay with that interpretation also. My doubt is about allowing userspace to map the MSI-X table, which is not currently allowed.
Actually ... it would be allowed and it would have an "undefined behavior" because of the sparse feature. So, perhaps you're right and it could be seen as a fix both ways: fixing undefined behavior and allowing the MSI-X table to be mmaped, which will allow better performance for QEMU.
After re-thinking, I'm +1 on the backport for Bionic Kernel also if others agree.