Hi, since [1] doesn't change the identifier (it stays gen15a), so the only thing that is changing is the description of e.g. seen here: $ qemu-system-s390x -cpu ? | grep gen15 s390 gen15a-base IBM 8561 GA1 (static, migration-safe) s390 gen15a IBM 8561 GA1 (migration-safe) s390 gen15b-base IBM 8562 GA1 (static, migration-safe) s390 gen15b IBM 8562 GA1 (migration-safe)
As far as I see it has no functional impact - is that correct? Under that assumption I'm considering this for Eoan as prio-medium (as it is still open), and for SRUs as whishlist. It might be added there "along" some other SRU later, but isn't reasonable on its own triggering downloads for millions of users - if you don't agree please outline why we'd need this any sooner there. FYI: Please note that changing the actual type "gen15a" to something else is even less of an option at least for SRUs as people could use it already and the update would break them. [1]: https://git.qemu.org/?p=qemu.git;a=commit;h=7505deca ** Changed in: qemu (Ubuntu Disco) Status: New => Triaged ** Changed in: qemu (Ubuntu Disco) Importance: Undecided => Wishlist ** Changed in: qemu (Ubuntu Bionic) Importance: Undecided => Wishlist ** Changed in: qemu (Ubuntu Bionic) Status: New => Triaged ** Changed in: qemu (Ubuntu) Status: New => In Progress ** Changed in: qemu (Ubuntu) Importance: Undecided => Medium ** Description changed: - SRU Justification: - ================== + SRU Justification Kernel: + ========================= [Impact] * Add / activate support for IBM z15 and LinuxONE III systems [Fix] * a0e2251132995b962281aa80ab54a9288f9e0b6b a0e2251 "s390: add support for IBM z15 machines" [Test Case] * check and verify cpuinfo - regression testing is possible by Canonical/me * functional testing is currently only doable by IBM [Regression Potential] * There is regression potential with having new code in and the flags added/active * but the code changes are pretty straight forward, just add config, cases and defs * and are not used on existing systems, just on the new generation that is not yet out in the field [Other Info] * SRU of LP 1842916 merged with (this) LP 1842774 + + --- + + SRU Template for qemu as the impact/scope is different + ====================================================== + + [Impact] + + * Update naming of the new HW Generation + + * Now that the systems are released people might look for types matching + the name and no one really knows "IBM 8561 GA1". + + * Help users to identify the cpu type by backporting the fix that sets the + defined name. + + [Fix] + + * https://git.qemu.org/?p=qemu.git;a=commit;h=7505deca + + [Test Case] + + * qemu-system-s390x -cpu ? | grep gen15 + s390 gen15a-base IBM 8561 GA1 (static, migration-safe) + s390 gen15a IBM 8561 GA1 (migration-safe) + s390 gen15b-base IBM 8562 GA1 (static, migration-safe) + s390 gen15b IBM 8562 GA1 (migration-safe) + + * With the fix gen15a should be called "IBM z15 GA1" + + [Regression Potential] + + * The only thing changing (for qemu) are some texts e.g. when showing CPU + types. The cpu type itself that is used in e.g. scripts / commands will + not change. Therefore the regression risk of the qemu change is next to + none. The only I can think of is people grepping for the old ID in text + output, but that seems theoretical and not important. + + [Other Info] + + * For an SRU perspective this is "nice to have" we will only do this + "along" other higher impact SRUs. + + __________ This feature request will provide the final naming of the next machine -- 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/1842774 Title: Enhanced Hardware Support - Finalize Naming Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in qemu source package in Bionic: Triaged Status in linux source package in Disco: In Progress Status in qemu source package in Disco: Triaged Bug description: SRU Justification Kernel: ========================= [Impact] * Add / activate support for IBM z15 and LinuxONE III systems [Fix] * a0e2251132995b962281aa80ab54a9288f9e0b6b a0e2251 "s390: add support for IBM z15 machines" [Test Case] * check and verify cpuinfo - regression testing is possible by Canonical/me * functional testing is currently only doable by IBM [Regression Potential] * There is regression potential with having new code in and the flags added/active * but the code changes are pretty straight forward, just add config, cases and defs * and are not used on existing systems, just on the new generation that is not yet out in the field [Other Info] * SRU of LP 1842916 merged with (this) LP 1842774 --- SRU Template for qemu as the impact/scope is different ====================================================== [Impact] * Update naming of the new HW Generation * Now that the systems are released people might look for types matching the name and no one really knows "IBM 8561 GA1". * Help users to identify the cpu type by backporting the fix that sets the defined name. [Fix] * https://git.qemu.org/?p=qemu.git;a=commit;h=7505deca [Test Case] * qemu-system-s390x -cpu ? | grep gen15 s390 gen15a-base IBM 8561 GA1 (static, migration-safe) s390 gen15a IBM 8561 GA1 (migration-safe) s390 gen15b-base IBM 8562 GA1 (static, migration-safe) s390 gen15b IBM 8562 GA1 (migration-safe) * With the fix gen15a should be called "IBM z15 GA1" [Regression Potential] * The only thing changing (for qemu) are some texts e.g. when showing CPU types. The cpu type itself that is used in e.g. scripts / commands will not change. Therefore the regression risk of the qemu change is next to none. The only I can think of is people grepping for the old ID in text output, but that seems theoretical and not important. [Other Info] * For an SRU perspective this is "nice to have" we will only do this "along" other higher impact SRUs. __________ This feature request will provide the final naming of the next machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1842774/+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
