From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: Sam Bobroff <sam.bobroff@au1.ibm.com>,
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: Re: [PATCH 3/3] selftests/powerpc: Add transactional syscall test
Date: Fri, 20 Mar 2015 14:55:41 +0530 [thread overview]
Message-ID: <550BE795.4070200@linux.vnet.ibm.com> (raw)
In-Reply-To: <b4a4ea23b20098512cf350b97ce98e0d1ea58531.1426740212.git.sam.bobroff@au1.ibm.com>
On 03/19/2015 10:13 AM, Sam Bobroff wrote:
> Check that a syscall made during an active transaction will fail with
> the correct failure code and that one made during a suspended
> transaction will succeed.
>
> Signed-off-by: Sam Bobroff <sam.bobroff@au1.ibm.com>
The test works.
> +
> +int tm_syscall(void)
> +{
> + SKIP_IF(!((long)get_auxv_entry(AT_HWCAP2) & PPC_FEATURE2_HTM));
> + setbuf(stdout, 0);
> + FAIL_IF(!t_active_getppid_test());
> + printf("%d active transactions correctly aborted.\n", TM_TEST_RUNS);
> + FAIL_IF(!t_suspended_getppid_test());
> + printf("%d suspended transactions succeeded.\n", TM_TEST_RUNS);
> + return 0;
> +}
> +
> +int main(void)
> +{
> + return test_harness(tm_syscall, "tm_syscall");
> +}
> +
There is an extra blank line at the end of this file. Interchanging return
codes of 0 and 1 for various functions make it very confusing along with
negative FAIL_IF checks in the primary test function. Control flow structures
like these can use some in-code documentation for readability.
+ for (i = 0; i < TM_RETRIES; i++) {
+ if (__builtin_tbegin(0)) {
+ getppid();
+ __builtin_tend(0);
+ return 1;
+ }
+ if (t_failure_persistent())
+ return 0;
or
+ if (__builtin_tbegin(0)) {
+ __builtin_tsuspend();
+ getppid();
+ __builtin_tresume();
+ __builtin_tend(0);
+ return 1;
+ }
+ if (t_failure_persistent())
+ return 0;
next prev parent reply other threads:[~2015-03-20 9:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 4:43 [PATCH 0/3] powerpc/tm: Abort syscalls in active transactions Sam Bobroff
2015-03-19 4:43 ` [PATCH 1/3] " Sam Bobroff
2015-03-19 5:01 ` Michael Neuling
2015-03-20 9:04 ` Anshuman Khandual
2015-03-24 2:04 ` Michael Ellerman
2015-03-24 4:26 ` Anshuman Khandual
2015-03-24 13:02 ` Michael Ellerman
2015-03-19 4:43 ` [PATCH 2/3] selftests/powerpc: Move get_auxv_entry() to harness.c Sam Bobroff
2015-03-19 4:43 ` [PATCH 3/3] selftests/powerpc: Add transactional syscall test Sam Bobroff
2015-03-20 9:25 ` Anshuman Khandual [this message]
2015-03-24 1:52 ` Sam Bobroff
2015-03-24 2:02 ` Michael Ellerman
2015-03-30 0:06 ` 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=550BE795.4070200@linux.vnet.ibm.com \
--to=khandual@linux.vnet.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 \
--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).