c000efe90198 not in .data!
[0.346491] DEBUG_LOCKS_WARN_ON(1)
[0.346502] [ cut here ]
[0.346504] WARNING: at ../kernel/locking/lockdep.c:3002
[0.346506] Modules linked in:
Reported-by: Gustavo Luiz Duarte
Signed-off-by: Sukadev Bhattiprolu
Tested-by
On 11/29/2016 01:42 AM, Michael Ellerman wrote:
Nicholas Piggin writes:
> On Mon, 28 Nov 2016 22:07:39 +1100
> Michael Ellerman wrote:
>> Nicholas Piggin writes:
>>> diff --git a/arch/powerpc/boot/wrapper b/arch/powerpc/boot/wrapper
>>> index 404b3aa..cd941a8 100755
>>> --- a/arch/powerpc/boo
the same bug, tm-signal-context-force-tm has a
better coverage, in the sense that by running the test several times it might
trigger the pagefault and/or be preempted at different places.
Signed-off-by: Gustavo Luiz Duarte
---
tools/testing/selftests/powerpc/tm/.gitignore | 1 +
tools/testing
;count' is changed within the signal handler, it is declared as
volatile to prevent any compiler optimization getting confused with
asynchronous changes.
Signed-off-by: Gustavo Luiz Duarte
---
.../powerpc/tm/tm-signal-context-force-tm.c | 79 +--
1 file changed, 37 in
it can
be exposed to the signal handler later in setup_tm_sigcontexts() to inform the
userspace MSR at the moment of the signal delivery.
Found with tm-signal-context-force-tm kernel selftest on P8 KVM.
Fixes: 2b0a576d15e0 ("powerpc: Add new transactional memory state to the signal
cont
the same bug, tm-signal-context-force-tm has a
better coverage, in the sense that by running the test several times it might
trigger the pagefault and/or be preempted at different places.
Signed-off-by: Gustavo Luiz Duarte
---
tools/testing/selftests/powerpc/tm/.gitignore | 1 +
tools/testing
sactional memory state to the signal
context")
Cc: sta...@vger.kernel.org # v3.9
Signed-off-by: Gustavo Luiz Duarte
---
arch/powerpc/kernel/signal.c| 17 +++--
arch/powerpc/kernel/signal_32.c | 28 ++--
arch/powerpc/kernel/signal_64.c | 22 ++
;count' is changed within the signal handler, it is declared as
volatile to prevent any compiler optimization getting confused with
asynchronous changes.
Signed-off-by: Gustavo Luiz Duarte
---
.../powerpc/tm/tm-signal-context-force-tm.c | 79 +--
1 file changed, 37 in
ls".
How about "powerpc/tm: Clear the current thread's MSR[TS] when
transaction is reclaimed on signal delivery" ?
On Mon, 2020-02-03 at 13:09 -0300, Gustavo Luiz Duarte wrote:
After a treclaim, we expect to be in non-transactional state. If we don't
immediately clear
On 2/5/20 2:27 AM, Michael Ellerman wrote:
Gustavo Luiz Duarte writes:
This test triggers a TM Bad Thing by raising a signal in transactional state
and forcing a pagefault to happen in kernelspace when the kernel signal
handling code first touches the user signal stack.
This is inspired by
werpc: Add new transactional memory state to the signal
context")
Cc: sta...@vger.kernel.org # v3.9
Signed-off-by: Gustavo Luiz Duarte
---
arch/powerpc/kernel/signal.c| 16 ++--
arch/powerpc/kernel/signal_32.c | 28 ++--
arch/powerpc/kernel/signal_64
the same bug, tm-signal-context-force-tm has a
better coverage, in the sense that by running the test several times it might
trigger the pagefault and/or be preempted at different places.
v3: skip test if userfaultfd is unavailable.
Signed-off-by: Gustavo Luiz Duarte
---
tools/testing/selftests
;count' is changed within the signal handler, it is declared as
volatile to prevent any compiler optimization getting confused with
asynchronous changes.
Signed-off-by: Gustavo Luiz Duarte
---
.../powerpc/tm/tm-signal-context-force-tm.c | 79 +--
1 file changed, 37 in
13 matches
Mail list logo
