From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: gromero <gromero@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, mikey@neuling.org
Cc: cyrilbur@gmail.com, gromero@linux.vnet.ibm.com
Subject: Re: [PATCH v2 3/3] powerpc/tm: Add tm-poison test
Date: Wed, 25 Sep 2019 21:05:18 +1000 (AEST) [thread overview]
Message-ID: <46dZwH2cgLz9sPL@ozlabs.org> (raw)
In-Reply-To: <20190904045529.23002-3-gromero@linux.vnet.ibm.com>
On Wed, 2019-09-04 at 04:55:29 UTC, gromero wrote:
> From: Gustavo Romero <gromero@linux.ibm.com>
>
> Add TM selftest to check if FP or VEC register values from one process
> can leak into another process when both run on the same CPU.
>
> Signed-off-by: Gustavo Romero <gromero@linux.ibm.com>
> Signed-off-by: Michael Neuling <mikey@neuling.org>
Applied to powerpc fixes, thanks.
https://git.kernel.org/powerpc/c/a003365cab64b0f7988ac3ccb1da895ce0bece5e
cheers
next prev parent reply other threads:[~2019-09-25 11:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 4:47 [PATCH 1/3] powerpc/tm: Fix FP/VMX unavailable exceptions inside a transaction Michael Neuling
2019-09-03 4:47 ` [PATCH 2/3] powerpc/tm: Fix restoring FP/VMX facility incorrectly on interrupts Michael Neuling
2019-09-03 4:47 ` [PATCH 3/3] powerpc/tm: Add tm-poison test Michael Neuling
2019-09-03 11:46 ` Michael Ellerman
2019-09-04 4:59 ` Gustavo Romero
2019-09-04 4:55 ` [PATCH v2 1/3] powerpc/tm: Fix FP/VMX unavailable exceptions inside a transaction gromero
2019-09-04 4:55 ` [PATCH v2 2/3] powerpc/tm: Fix restoring FP/VMX facility incorrectly on interrupts gromero
2019-09-05 12:05 ` Michael Ellerman
2019-09-04 4:55 ` [PATCH v2 3/3] powerpc/tm: Add tm-poison test gromero
2019-09-25 11:05 ` Michael Ellerman [this message]
2019-09-05 12:05 ` [PATCH v2 1/3] powerpc/tm: Fix FP/VMX unavailable exceptions inside a transaction 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=46dZwH2cgLz9sPL@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=cyrilbur@gmail.com \
--cc=gromero@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.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).