== Comment: #0 - Breno Henrique Leitao <[email protected]> - 2017-02-14 10:03:03 == We don't support transactional memory in PR KVM, so don't tell the OS that we do.
These are the required patches: commit 2e68f28854f0120c9a938a61b64aaf1eaecb162b Author: Thomas Huth <[email protected]> Date: Wed Sep 28 13:16:30 2016 +0200 ppc: Check the availability of transactional memory KVM-PR currently does not support transactional memory, and the implementation in TCG is just a fake. We should not announce TM support in the ibm,pa-features property when running on such a system, so disable it by default and only enable it if the KVM implementation supports it (i.e. recent versions of KVM-HV). These changes are based on some earlier work from Anton Blanchard (thanks!). Signed-off-by: Thomas Huth <[email protected]> Reviewed-by: C?dric Le Goater <[email protected]> Signed-off-by: David Gibson <[email protected]> (cherry picked from commit bac3bf287ab60e264b636f5f00c116a19b655762) commit 45a4f18e2ec40b96893c780c28ab18c246906355 Author: Thomas Huth <[email protected]> Date: Wed Sep 28 13:16:29 2016 +0200 hw/ppc/spapr: Fix the selection of the processor features The current code uses pa_features_206 for POWERPC_MMU_2_06, and for everything else, it uses pa_features_207. This is bad in some cases because there is also a "degraded" MMU version of ISA 2.06, called POWERPC_MMU_2_06a, which should of course use the flags for 2.06 instead. And there is also the possibility that the user runs the pseries machine with a POWER5+ or even 970 processor. In that case we certainly do not want to set the flags for 2.07, and rather simply skip the setting of the pa-features property instead. Signed-off-by: Thomas Huth <[email protected]> Reviewed-by: C?dric Le Goater <[email protected]> Signed-off-by: David Gibson <[email protected]> (cherry picked from commit 4cbec30d769a73853b60dc7f275e6e7da9ab5162) commit 5c179666057a7568306062e2cd030042a25eb57a Author: Thomas Huth <[email protected]> Date: Wed Sep 28 13:16:28 2016 +0200 hw/ppc/spapr: Move code related to "ibm,pa-features" to a separate function The function spapr_populate_cpu_dt() has become quite big already, and since we likely have to extend the pa-features property for every new processor generation, it is nicer if we put the related code into a separate function. Signed-off-by: Thomas Huth <[email protected]> Reviewed-by: C?dric Le Goater <[email protected]> Signed-off-by: David Gibson <[email protected]> (cherry picked from commit 230bf719d3a3b144a4ffa441e5d6170ef0ad8999) Hi 1. what releases are you think need to get fixed? I didn't check yet, but you might already know. 2. Could you quickly check if we can close bug 1660946 as dup to this one? They seem so similar at least to me. According to qemu git the patches are all in >=v2.7.1 Since zesty already holds 2.8 setting status accordingly. Assuming you request Xenial for now, but as asked in comment #1.1 - please share your intentions where this has to go to. If you meant Xenial, do you have checked back-portability of those? Also don't miss #1.2 as it would help to work on these as one. Hi Christian, 1) We would like to have it fixed in 16.04. 2) Yes, unfortunately I didn't find 1660946, thus, opened this one. Both of them requires the same fix, and one of them could be dup. On Tue, Feb 14, 2017 at 2:32 PM, ChristianEhrhardt < [email protected]> wrote: > Hi > 1. what releases are you think need to get fixed? > I didn't check yet, but you might already know. > > 2. Could you quickly check if we can close bug 1660946 as dup to this one? > They seem so similar at least to me. > > -- > You received this bug notification because you are a member of Taco > Screen team, which is a bug assignee. > https://bugs.launchpad.net/bugs/1664622 > > Title: > qemu: Missing transaction memory advertisement > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1664622/+subscriptions > Status changed to 'Confirmed' because the bug affects multiple users. Thanks, I was comparing your suggestion: http://git.qemu-project.org/?p=qemu.git;a=commitdiff;h=2e68f28854f0120c9a938a61b64aaf1eaecb162b http://git.qemu-project.org/?p=qemu.git;a=commitdiff;h=45a4f18e2ec40b96893c780c28ab18c246906355 http://git.qemu-project.org/?p=qemu.git;a=commitdiff;h=5c179666057a7568306062e2cd030042a25eb57a With Thomas who pointed out (only) to: http://git.qemu-project.org/?p=qemu.git;a=commitdiff;h=bac3bf287ab60e264b6 Now of these 2e68f288 and bac3bf28 are the same. Just one being 2.8 dev and one the 2.7.1 stable backport cherry pick. The others you listed here seem to be more from 2.7.1. Since the changes are from Thomas I'd hope he can tell us if we only need one or all three. I think you need at least also the first patch that moves the code into a separate function. Otherwise you'll have to resolve the conflicts manually. Preliminary builds as preparation for an SRU currently building at Xenial https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2502 Yakkety https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2503 My testing will start on those, but if you can please give it as much testing as you can as well. Tests for any regressions on the ppa look good so far, going to try to test the fixed case explicitly. If the Openstack CI team (from the dupped bug) could test that in their env as well that would be great. Christian, I just tested Xenial's ppa[1] and confirm it works. [1] https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2502 Thanks! Thanks Rafael, I'm already testing myself and updating the description to have a proper SRU Template then. I have to wait on confirmation on two more bugs which shall be part of this SRU (one need special HW and one needs better repro steps) - once those are resolved or dropped from the SRU this will move on to upload/proposed. Note: for testing, please do note that there seems also a guest kernel fix to tolerate that as the iso of 16.04.2 works with and without the fix for me - and at this stage it should only be the newer kernel/initrd that matters. @Rafael - in your tests did you test with the same ISO as in the past or did you happen to use the just released 16.04.2 iso? Not that we fail- assume it is fixed now. @Christian, good catch. I apologize for reporting a false positive. Looks like all what matters is the kernel version. I was able to boot new ISO images with regular qemu provided, but failed to boot old ISOs. I've used this one http://ports.ubuntu.com/ubuntu-ports/dists/xenial-updates/main/installer-ppc64el/current/images/netboot/mini.iso. 2017-02-15 14:05 64M With the current iso, it works. Still getting HTM exception with old iso... even updating to new qemu from ppa: http://ports.ubuntu.com/ubuntu-ports/dists/xenial-updates/main/installer-ppc64el/20101020ubuntu451.6/images/netboot/mini.iso 2016-10-12 12:32 62M -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1664622 Title: qemu: Missing transaction memory advertisement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1664622/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
