https://lists.ubuntu.com/archives/kernel-team/2017-March/082814.html
** Also affects: linux (Ubuntu Zesty)
Importance: High
Assignee: Canonical Kernel Team (canonical-kernel-team)
Status: Triaged
** Also affects: linux (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Zesty)
Status: Triaged => Fix Released
** Changed in: linux (Ubuntu Zesty)
Assignee: Canonical Kernel Team (canonical-kernel-team) => (unassigned)
** Changed in: linux (Ubuntu Yakkety)
Status: New => In Progress
** Changed in: linux (Ubuntu Yakkety)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
--
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/1669023
Title:
Kernel: Fix Transactional memory config typo
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Yakkety:
In Progress
Status in linux source package in Zesty:
Fix Released
Bug description:
Canonical,
Please include the following fix on 16.10. This typo is causing some issue
on TM.
The patches that causes this problem is
ec2a04841b785373a6379af66032201a2b90922b on yakkety-ubuntu repo.
commit 39715bf972ed4fee18fe5409609a971fb16b1771
Author: Valentin Rothberg <valentinrothb...@gmail.com>
Date: Wed Oct 5 07:57:26 2016 +0200
powerpc/process: Fix CONFIG_ALIVEC typo in restore_tm_state()
It should be ALTIVEC, not ALIVEC.
Cyril explains: If a thread performs a transaction with altivec and then
gets preempted for whatever reason, this bug may cause the kernel to not
re-enable altivec when that thread runs again. This will result in an
altivec unavailable fault, when that fault happens inside a user
transaction the kernel has no choice but to enable altivec and doom the
transaction.
The result is that transactions using altivec may get aborted more often
than they should.
The difficulty in catching this with a selftest is my deliberate use of
the word may above. Optimisations to avoid FPU/altivec/VSX faults mean
that the kernel will always leave them on for 255 switches. This code
prevents the kernel turning it off if it got to the 256th switch (and
userspace was transactional).
Fixes: dc16b553c949 ("powerpc: Always restore FPU/VEC/VSX if hardware
transactional memory in use")
Reviewed-by: Cyril Bur <cyril...@gmail.com>
Signed-off-by: Valentin Rothberg <valentinrothb...@gmail.com>
Signed-off-by: Michael Ellerman <m...@ellerman.id.au>
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1669023/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
