From: Sam Bobroff <sam.bobroff@au1.ibm.com>
To: mpe@ellerman.id.au, benh@kernel.crashing.org
Cc: mikey@neuling.org, azanella@linux.vnet.ibm.com,
linuxppc-dev@lists.ozlabs.org, matt@ozlabs.org
Subject: [PATCH v3 0/4] powerpc/tm: Abort syscalls in active transactions
Date: Tue, 7 Apr 2015 10:54:46 +1000 [thread overview]
Message-ID: <cover.1428368031.git.sam.bobroff@au1.ibm.com> (raw)
See the first patch for a description of the reasoning behind this
change.
This set includes the change, a kernel selftest for it and
some slight refactoring of the selftest code.
v3:
Patch 1/4: powerpc/tm: Abort syscalls in active transactions
Use "TABORT()" macro to allow building on versions of gcc that don't support
the "tabort." instruction.
v2:
Patch 1/4: powerpc/tm: Abort syscalls in active transactions
Also update the failure code table.
Patch 3/4: selftests/powerpc: Add transactional syscall test
Further testing has shown that the success or failure of the transactions was
affected by minor changes to the code, compiler optimisation and linker
settings.
To address this, I've moved the transactional part of the test to a separate
function, written in assembly. I've also extended the test to as many
transactions as it can fit into ten seconds, to better test for failures that
occur more rarely. This has stabilised the results, and it's no longer
necessary to use special compiler or linker flags.
Patch 4/4: powerpc/tm: Correct minor documentation typos
Discovered some typos while updating the documentation.
Sam Bobroff (4):
powerpc/tm: Abort syscalls in active transactions
selftests/powerpc: Move get_auxv_entry() to harness.c
selftests/powerpc: Add transactional syscall test
powerpc/tm: Correct minor documentation typos
Documentation/powerpc/transactional_memory.txt | 36 +++----
arch/powerpc/include/uapi/asm/tm.h | 2 +-
arch/powerpc/kernel/entry_64.S | 19 ++++
tools/testing/selftests/powerpc/harness.c | 47 +++++++++
tools/testing/selftests/powerpc/pmu/lib.c | 47 ---------
tools/testing/selftests/powerpc/pmu/lib.h | 1 -
tools/testing/selftests/powerpc/tm/.gitignore | 1 +
tools/testing/selftests/powerpc/tm/Makefile | 4 +-
.../testing/selftests/powerpc/tm/tm-syscall-asm.S | 27 +++++
.../testing/selftests/powerpc/tm/tm-syscall-asm.h | 2 +
tools/testing/selftests/powerpc/tm/tm-syscall.c | 109 ++++++++++++++++++++
tools/testing/selftests/powerpc/utils.h | 2 +-
12 files changed, 228 insertions(+), 69 deletions(-)
create mode 100644 tools/testing/selftests/powerpc/tm/tm-syscall-asm.S
create mode 100644 tools/testing/selftests/powerpc/tm/tm-syscall-asm.h
create mode 100644 tools/testing/selftests/powerpc/tm/tm-syscall.c
--
1.7.10.4
next reply other threads:[~2015-04-07 0:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 0:54 Sam Bobroff [this message]
2015-04-07 0:54 ` [PATCH v3 1/4] powerpc/tm: Abort syscalls in active transactions Sam Bobroff
2015-04-07 0:54 ` [PATCH v3 2/4] selftests/powerpc: Move get_auxv_entry() to harness.c Sam Bobroff
2015-04-07 0:54 ` [PATCH v3 3/4] selftests/powerpc: Add transactional syscall test Sam Bobroff
2015-04-07 0:54 ` [PATCH v3 4/4] powerpc/tm: Correct minor documentation typos Sam Bobroff
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=cover.1428368031.git.sam.bobroff@au1.ibm.com \
--to=sam.bobroff@au1.ibm.com \
--cc=azanella@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=matt@ozlabs.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
/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).