From: Michael Ellerman <patch-notifications@ellerman•id.au>
To: Gustavo Romero <gromero@linux•vnet.ibm.com>,
linuxppc-dev@lists•ozlabs.org
Cc: cyrilbur@gmail•com, gromero@linux•vnet.ibm.com
Subject: Re: selftests/powerpc: Skip tm-unavailable if TM is not enabled
Date: Wed, 14 Mar 2018 20:28:39 +1100 (AEDT) [thread overview]
Message-ID: <401RHH24wVz9sVh@ozlabs.org> (raw)
In-Reply-To: <1520282935-20111-2-git-send-email-gromero@linux.vnet.ibm.com>
On Mon, 2018-03-05 at 20:48:55 UTC, Gustavo Romero wrote:
> Some processor revisions do not support transactional memory, and
> additionally kernel support can be disabled. In either case the
> tm-unavailable test should be skipped, otherwise it will fail with
> a SIGILL.
>
> That commit also sets this selftest to be called through the test
> harness as it's done for other TM selftests.
>
> Finally, it avoids using "ping" as a thread name since it's
> ambiguous and can be confusing when shown, for instance,
> in a kernel backtrace log.
>
> Fixes: 77fad8bfb1d2 ("selftests/powerpc: Check FP/VEC on exception in TM")
> Signed-off-by: Gustavo Romero <gromero@linux•vnet.ibm.com>
> Reviewed-by: Cyril Bur <cyrilbur@gmail•com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/b395e55b49ecd56ea28dc629f4ca4c
cheers
prev parent reply other threads:[~2018-03-14 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 20:48 [PATCH] Fixes for selftest tm-unavailable Gustavo Romero
2018-03-05 20:48 ` [PATCH] selftests/powerpc: Skip tm-unavailable if TM is not enabled Gustavo Romero
2018-03-05 23:49 ` Cyril Bur
2018-03-06 20:24 ` Gustavo Romero
2018-03-14 9:28 ` Michael Ellerman [this message]
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=401RHH24wVz9sVh@ozlabs.org \
--to=patch-notifications@ellerman$(echo .)id.au \
--cc=cyrilbur@gmail$(echo .)com \
--cc=gromero@linux$(echo .)vnet.ibm.com \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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