--
Shawn Landden
--
Shawn Landden
This even allows simd in preemptible kernel code,
as does x86, although this is rarely safe (could be used with
kthread_create_on_cpu). All callers are disabling preemption.
v4: fix build without CONFIG_AVX
change commit message
Signed-off-by: Shawn Landden
---
arch/powerpc/include/asm
Based off the x86 one.
WireGuard really wants to be able to do SIMD in interrupts,
so it can accelerate its in-bound path.
v4: allow using the may_use_simd symbol even when it always
returns false (via include guards)
Signed-off-by: Shawn Landden
---
arch/powerpc/include/asm/simd.h | 17
Hi
El mié., 15 may. 2019 5:17, Christophe Leroy
escribió:
> Hi,
>
> Le 15/05/2019 à 12:09, Christian Zigotzky a écrit :
> > Hi All,
> >
> > I got the following error messages with the latest Git kernel today:
> >
> > GEN .version
> >CHK include/generated/compile.h
> >LD
On Wed, May 15, 2019 at 1:27 AM Christophe Leroy
wrote:
> Could you please as usual list here the changes provided by each version
> to ease the review ?
A bunch of embarrassing stuff that caused it not to build on some
set-ups (the functions were under the wrong include guards), and I
added
This second patch is separate because it could be wrong,
like I am not sure about how kernel thread migration works,
and it is even allowing simd in preemptible kernel code.
v4: fix build without CONFIG_AVX
Signed-off-by: Shawn Landden
---
arch/powerpc/include/asm/switch_to.h | 15 +---
arch
Based off the x86 one.
WireGuard really wants to be able to do SIMD in interrupts,
so it can accelerate its in-bound path.
Signed-off-by: Shawn Landden
---
arch/powerpc/include/asm/simd.h | 17 +
arch/powerpc/kernel/process.c | 30 ++
2 files
Based off the x86 one.
WireGuard really wants to be able to do SIMD in interrupts,
so it can accelerate its in-bound path.
Signed-off-by: Shawn Landden
---
arch/powerpc/include/asm/simd.h | 17 +
arch/powerpc/kernel/process.c | 30 ++
2 files
8AM -0300, Shawn Landden wrote:
> > ARM does this, so we might as well too.
> > I am a bit confused however as CONFIG_ALTIVEC does not select
> > CONFIG_PPC_FPU. Would you ever have altivec without a fpu?
>
> There is no hardware like that, none supported anyway. It does
On Tue, May 14, 2019 at 12:43 AM Benjamin Herrenschmidt
wrote:
>
> On Mon, 2019-05-13 at 22:44 -0300, Shawn Landden wrote:
> > +
> > +/*
> > + * Were we in user mode when we were
> > + * interrupted?
> > + *
> > + * Doing kernel_altiv
On Tue, May 14, 2019 at 2:22 AM Russell Currey wrote:
>
> On Mon, 2019-05-13 at 23:23 -0300, Shawn Landden wrote:
> > This second patch is separate because it could be wrong,
> > like I am not sure about how kernel thread migration works,
> > and it is even allowing si
This second patch is separate because it could be wrong,
like I am not sure about how kernel thread migration works,
and it is even allowing simd in preemptible kernel code.
Signed-off-by: Shawn Landden
---
arch/powerpc/include/asm/switch_to.h | 15 ++-
arch/powerpc/kernel/process.c
Based off the x86 one.
WireGuard really wants to be able to do SIMD in interrupts,
so it can accelerate its in-bound path.
Signed-off-by: Shawn Landden
---
arch/powerpc/include/asm/simd.h | 17 +
arch/powerpc/kernel/process.c | 30 ++
2 files
ARM does this, so we might as well too.
I am a bit confused however as CONFIG_ALTIVEC does not select
CONFIG_PPC_FPU. Would you ever have altivec without a fpu?
Signed-off-by: Shawn Landden
---
arch/powerpc/include/asm/simd.h | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch
This second patch is separate because it could be wrong,
like I am not sure about how kernel thread migration works,
and it is even allowing simd in preemptible kernel code.
Signed-off-by: Shawn Landden
---
arch/powerpc/include/asm/switch_to.h | 15 ++-
arch/powerpc/kernel/process.c
Based off the x86 one.
WireGuard really wants to be able to do SIMD in interrupts,
so it can accelerate its in-bound path.
Signed-off-by: Shawn Landden
---
arch/powerpc/include/asm/simd.h | 10 ++
arch/powerpc/kernel/process.c | 30 ++
2 files changed, 40
This second patch is separate because it could be wrong,
like I am not sure about how kernel thread migration works,
and it is even allowing simd in preemptible kernel code.
Signed-off-by: Shawn Landden
---
arch/powerpc/include/asm/simd.h | 8 +
arch/powerpc/include/asm/switch_to.h
Based off the x86 one.
WireGuard really wants to be able to do SIMD in interrupts,
so it can accelerate its in-bound path.
Signed-off-by: Shawn Landden
---
arch/powerpc/include/asm/simd.h | 13 +
arch/powerpc/kernel/process.c | 30 ++
2 files changed
://bugzilla.kernel.org/show_bug.cgi?id=203571
Signed-off-by: Shawn Landden
---
arch/powerpc/include/asm/simd.h | 15 +++
1 file changed, 15 insertions(+)
create mode 100644 arch/powerpc/include/asm/simd.h
diff --git a/arch/powerpc/include/asm/simd.h b/arch/powerpc/include/asm/simd.h
new file mode
this linuxppc-dev didn't seem to accept it.
Buglink: https://bugzilla.kernel.org/show_bug.cgi?id=203571
Signed-off-by: Shawn Landden
---
arch/powerpc/include/asm/simd.h | 15 +++
1 file changed, 15 insertions(+)
create mode 100644 arch/powerpc/include/asm/simd.h
diff --git a/arch/powerpc
21 matches
Mail list logo