--- Comment From sathe...@in.ibm.com 2019-03-13 02:57 EDT---
Tested with below levels:
Host Kernel: 4.15.0-46-generic #49~16.04.1-Ubuntu SMP Tue Feb 12
17:43:02 UTC 2019 ppc64le
# cd /sys/firmware/devicetree/base/ibm,opal/fw-features
# ls -1 */enabled
fw-branch-hints-honored/enabled
--- Comment From sura...@au1.ibm.com 2019-02-06 18:11 EDT---
I have backported the 3 patches I mentioned previously and pushed a tree here:
https://github.com/sjitindarsingh/qemu/tree/ubuntu-xenial-devel
Note rework of "b2540203bd: ppc/spapr_caps: Don't disable cap_cfpc on
POWER8 by
--- Comment From sathe...@in.ibm.com 2019-02-04 05:09 EDT---
(In reply to comment #35)
> Hi,
>
> 8c5909c419 ppc/spapr-caps: Change migration macro to take full spapr-cap name
>
> Was part of my original backport and so should already be present. But as
> has already been said, this is
--- Comment From sthou...@in.ibm.com 2019-02-04 04:28 EDT---
(In reply to comment #35)
> Hi,
>
> 8c5909c419 ppc/spapr-caps: Change migration macro to take full spapr-cap name
>
> Was part of my original backport and so should already be present. But as
> has already been said, this is
--- Comment From sura...@au1.ibm.com 2019-01-13 19:50 EDT---
Hi,
8c5909c419 ppc/spapr-caps: Change migration macro to take full spapr-cap
name
Was part of my original backport and so should already be present. But as has
already been said, this is purely
cosmetic.
The following 3
--- Comment From mranw...@us.ibm.com 2019-01-11 01:58 EDT---
I talked to Michael Roth on this. It looks like everything is there for
spectre mitigation but there's two patches to allow power 8 guests to use
cap_cfpc=workaround:
072f416a53: target/ppc: Don't require private l1d cache on
--- Comment From sathe...@in.ibm.com 2018-09-25 13:55 EDT---
(In reply to comment #27)
> The test package is for Xenial, not for Trusty. Does that installation
> failure affect Xenial also?
my bad, mistaken it for Trusty.
Xenial installation has no issues, and tested the qemu package
--- Comment From sathe...@in.ibm.com 2018-09-21 14:06 EDT---
(In reply to comment #25)
> ping?
Hitting and blocked with installation failure for Trusty ,
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1792948/comments/3.
Pls suggest in case of any alternative ways to test.
Thanks
--- Comment From sura...@au1.ibm.com 2018-08-01 02:08 EDT---
Patches backported to xenial-devel and pushed here:
https://github.com/sjitindarsingh/qemu/tree/ubuntu-xenial-devel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--- Comment From sura...@au1.ibm.com 2018-07-30 22:03 EDT---
Taking a look at bionic-devel, it looks like all the relevant patches have
already been backported as of 13 Jun.
commit 88bd38f84c0ec61729f2502cc87613186e36da81
Author: Christian Ehrhardt
Date: Wed Jun 13 10:41:34 2018 +0200
--- Comment From sura...@au1.ibm.com 2018-07-23 01:57 EDT---
Happy to do the backport.
But can someone point me to where I can find the relevant ubuntu qemu trees the
patches need to apply to?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
--- Comment From bar...@us.ibm.com 2018-07-17 15:43 EDT---
Each company might be waiting on each other for this one.
To clarify: Is Canonical's request for IBM to provide complete backports for
qemu in versions 14.04 and 16.04, supplemental information to the qemu commit
list provided
--- Comment From sura...@au1.ibm.com 2018-06-18 23:22 EDT---
Is a list of the relevant kernel patches still required for this bug?
What help is required for this backport?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
13 matches
Mail list logo