From: Rashmica <rashmicy@gmail.com>
To: Anshuman Khandual <khandual@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 2/3] selftests/powerpc: Add test for forking inside transaction
Date: Wed, 2 Dec 2015 10:31:00 +1100 [thread overview]
Message-ID: <565E2DB4.4030908@gmail.com> (raw)
In-Reply-To: <565D563F.3010709@linux.vnet.ibm.com>
As far as I'm aware, the kernel used to crash when forking inside a
transaction (see powerpc/tm: Fix crash when forking inside a
transaction). So this is to check that the transaction aborts rather
than your whole kernel crashing.
On 01/12/15 19:11, Anshuman Khandual wrote:
> On 12/01/2015 10:38 AM, Rashmica Gupta wrote:
>> +int test_fork(void)
>> +{
>> + SKIP_IF(!have_htm());
>> +
>> + asm __volatile__(
>> + "tbegin.;"
>> + "blt 1f; "
>> + "li 0, 2;" /* fork syscall */
>> + "sc ;"
>> + "tend.;"
>> + "1: ;"
>> + : : : "memory", "r0");
>> + /* If we reach here, we've passed. Otherwise we've probably crashed
>> + * the kernel */
> The transaction inside the parent process will abort. What
> is expected inside the child process ? Why should the kernel
> crash ?
>
next prev parent reply other threads:[~2015-12-01 23:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 5:08 [PATCH 0/3] selftests/powerpc: Transactional Memory Rashmica Gupta
2015-12-01 5:08 ` [PATCH 1/3] selftests/powerpc: Standardise TM calls Rashmica Gupta
2015-12-01 8:08 ` Anshuman Khandual
2015-12-02 3:40 ` Michael Ellerman
2015-12-02 4:41 ` Anshuman Khandual
2015-12-01 5:08 ` [PATCH 2/3] selftests/powerpc: Add test for forking inside transaction Rashmica Gupta
2015-12-01 8:11 ` Anshuman Khandual
2015-12-01 23:31 ` Rashmica [this message]
2015-12-02 5:27 ` Michael Neuling
2015-12-01 5:08 ` [PATCH 3/3] selftests/powerpc: Add in check for TM Rashmica Gupta
2015-12-01 5:18 ` [PATCH 0/3] selftests/powerpc: Transactional Memory Andrew Donnellan
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=565E2DB4.4030908@gmail.com \
--to=rashmicy@gmail.com \
--cc=khandual@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
/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).