From: Michael Neuling <mikey@neuling.org>
To: mpe@ellerman.id.au, benh@kernel.crashing.org
Cc: mikey@neuling.org, sam.bobroff@au1.ibm.com,
linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: [PATCH v2 0/3] powerpc/tm: MSR oops printing and selftests
Date: Fri, 20 Nov 2015 15:15:31 +1100 [thread overview]
Message-ID: <1447992934-18905-1-git-send-email-mikey@neuling.org> (raw)
Here are 3 non-urgent TM patches. These were left off my other post
of the urgent fixes.
v2:
- Added invalid stack with signal delievery during tm selftest
- Added selftest binaries to .gitignore
- Improved signal return selftest based on mpe's feedback
- Improved oops message printing based on mpe's feedback
- Dropped get_tm_stackpointer() renaming patch in leui of more
extensive rewrite later
Michael Neuling (3):
powerpc: Print MSR TM bits in oops message
selftests/powerpc: Add TM signal return test
selftests/powerpc: Add TM signal with invalid stack test
arch/powerpc/kernel/process.c | 51 ++++++++++++---
tools/testing/selftests/powerpc/tm/.gitignore | 2 +
tools/testing/selftests/powerpc/tm/Makefile | 2 +-
.../selftests/powerpc/tm/tm-signal-msr-resv.c | 71 +++++++++++++++++++++
.../testing/selftests/powerpc/tm/tm-signal-stack.c | 73 ++++++++++++++++++++++
5 files changed, 190 insertions(+), 9 deletions(-)
create mode 100644 tools/testing/selftests/powerpc/tm/tm-signal-msr-resv.c
create mode 100644 tools/testing/selftests/powerpc/tm/tm-signal-stack.c
--
2.5.0
next reply other threads:[~2015-11-20 4:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 4:15 Michael Neuling [this message]
2015-11-20 4:15 ` [PATCH v2 1/3] powerpc: Print MSR TM bits in oops messages Michael Neuling
2015-12-15 11:27 ` [v2,1/3] " Michael Ellerman
2015-11-20 4:15 ` [PATCH v2 2/3] selftests/powerpc: Add TM signal return test Michael Neuling
2015-11-23 11:32 ` Anshuman Khandual
2015-12-15 11:27 ` [v2,2/3] " Michael Ellerman
2015-11-20 4:15 ` [PATCH v2 3/3] selftests/powerpc: Add TM signal with invalid stack test Michael Neuling
2015-11-23 11:32 ` Anshuman Khandual
2015-12-15 11:27 ` [v2, " Michael Ellerman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1447992934-18905-1-git-send-email-mikey@neuling.org \
--to=mikey@neuling.org \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=sam.bobroff@au1.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).