From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/5] powerpc: Test MSR_FP and MSR_VEC when enabling/flushing VSX
Date: Wed, 16 Aug 2017 16:02:26 +1000 [thread overview]
Message-ID: <1502863346.4493.78.camel@kernel.crashing.org> (raw)
In-Reply-To: <20170816060118.24803-1-benh@kernel.crashing.org>
On Wed, 2017-08-16 at 16:01 +1000, Benjamin Herrenschmidt wrote:
> VSX uses a combination of the old vector registers, the old FP registers
> and new "second halves" of the FP registers.
>
> Thus when we need to see the VSX state in the thread struct
> (flush_vsx_to_thread) or when we'll use the VSX in the kernel
> (enable_kernel_vsx) we need to ensure they are all flushed into
> the thread struct if either of them is individually enabled.
>
> Unfortunately we only tested if the whole VSX was enabled, not
> if they were individually enabled.
>
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
And CC stable.
> ---
> arch/powerpc/kernel/process.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/arch/powerpc/kernel/process.c b/arch/powerpc/kernel/process.c
> index 9f3e2c932dcc..883216b4296a 100644
> --- a/arch/powerpc/kernel/process.c
> +++ b/arch/powerpc/kernel/process.c
> @@ -362,7 +362,8 @@ void enable_kernel_vsx(void)
>
> cpumsr = msr_check_and_set(MSR_FP|MSR_VEC|MSR_VSX);
>
> - if (current->thread.regs && (current->thread.regs->msr & MSR_VSX)) {
> + if (current->thread.regs &&
> + (current->thread.regs->msr & (MSR_VSX|MSR_VEC|MSR_FP))) {
> check_if_tm_restore_required(current);
> /*
> * If a thread has already been reclaimed then the
> @@ -386,7 +387,7 @@ void flush_vsx_to_thread(struct task_struct *tsk)
> {
> if (tsk->thread.regs) {
> preempt_disable();
> - if (tsk->thread.regs->msr & MSR_VSX) {
> + if (tsk->thread.regs->msr & (MSR_VSX|MSR_VEC|MSR_FP)) {
> BUG_ON(tsk != current);
> giveup_vsx(tsk);
> }
next prev parent reply other threads:[~2017-08-16 6:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 6:01 [PATCH 1/5] powerpc: Test MSR_FP and MSR_VEC when enabling/flushing VSX Benjamin Herrenschmidt
2017-08-16 6:01 ` [PATCH 2/5] powerpc: Fix missing CR before { Benjamin Herrenschmidt
2017-08-18 12:51 ` [2/5] " Michael Ellerman
2017-08-16 6:01 ` [PATCH 3/5] powerpc: Remove redundant fp/altivec giveup code Benjamin Herrenschmidt
2017-08-16 6:01 ` [PATCH 4/5] powerpc: Remove redundant clear of MSR_VSX in __giveup_vsx() Benjamin Herrenschmidt
2017-08-16 6:01 ` [PATCH 5/5] powerpc: Remove more redundant VSX save/tests Benjamin Herrenschmidt
2017-08-16 6:02 ` Benjamin Herrenschmidt [this message]
2017-08-17 13:03 ` [1/5] powerpc: Test MSR_FP and MSR_VEC when enabling/flushing VSX 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=1502863346.4493.78.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--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).