All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linuxppc-dev@lists.ozlabs.org
Subject: [PATCH 3/5] powerpc: Remove redundant fp/altivec giveup code
Date: Wed, 16 Aug 2017 16:01:16 +1000	[thread overview]
Message-ID: <20170816060118.24803-3-benh@kernel.crashing.org> (raw)
In-Reply-To: <20170816060118.24803-1-benh@kernel.crashing.org>

__giveup_vsx already calls those two functions

Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
---
 arch/powerpc/kernel/process.c | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/arch/powerpc/kernel/process.c b/arch/powerpc/kernel/process.c
index 14b9a3c46c5d..bfbd6083f841 100644
--- a/arch/powerpc/kernel/process.c
+++ b/arch/powerpc/kernel/process.c
@@ -375,10 +375,6 @@ void enable_kernel_vsx(void)
 		 */
 		if(!msr_tm_active(cpumsr) && msr_tm_active(current->thread.regs->msr))
 			return;
-		if (current->thread.regs->msr & MSR_FP)
-			__giveup_fpu(current);
-		if (current->thread.regs->msr & MSR_VEC)
-			__giveup_altivec(current);
 		__giveup_vsx(current);
 	}
 }
-- 
2.13.4

  parent reply	other threads:[~2017-08-16  6:01 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 ` Benjamin Herrenschmidt [this message]
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 ` [PATCH 1/5] powerpc: Test MSR_FP and MSR_VEC when enabling/flushing VSX Benjamin Herrenschmidt
2017-08-17 13:03 ` [1/5] " 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=20170816060118.24803-3-benh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.