From: Guo Ren <guoren@kernel.org>
To: Andy Chiu <andy.chiu@sifive.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
vineetg@rivosinc.com, bjorn@kernel.org, greentime.hu@sifive.com,
paul.walmsley@sifive.com, guoren@linux.alibaba.com,
anup@brainfault.org, atishp@atishpatra.org,
heiko.stuebner@vrull.eu, Albert Ou <aou@eecs.berkeley.edu>
Subject: Re: [v2, 0/5] riscv: support kernel-mode Vector
Date: Wed, 16 Aug 2023 19:18:53 -0400 [thread overview]
Message-ID: <ZN1ZXcwYZtABNdUy@gmail.com> (raw)
In-Reply-To: <20230721112855.1006-1-andy.chiu@sifive.com>
On Fri, Jul 21, 2023 at 11:28:50AM +0000, Andy Chiu wrote:
> This series provides support for running Vector code in kernel mode. The
> implementation is based on the v12 series of the Vector series, but with
> some additions. First, we introduce a mechanism to defer restoring
> Vector context for userspace programs (patch 1). This is similar to
> arm64 and x86's approaches when dealing with extra userspace register
> context. And it is benefitial to both Vector in user and kernel-mode.
> Then, patch 2, 3 add the kernel-mode Vector patch from v12 with minor
> modifications. At the end of the series, patch 4, 5 add supports for
> making kernel-mode Vector code preemptible. We do this by adding
> kernel-mode Vector context, and keeping track of the frame where V
> context is last valid. We believe that enabling preemption of running V
> is a critical path for getting V more generally available in the
> kernel-mode. Besides, with status.VS, we can easily tell if
> saving/restoring V is required. This reduce the level of cost when
> running SIMD in kernel mode as compared to other arches. Other arches
> usually do not have a way to tell if extra context is dirty. Thus, if
> they also want to support running preemptible code with extra registers,
> then they must save/restore extra context at each context switch even if
> registers are not dirty.
>
> The series is tested by loading a kernel module on a preemptive kernel.
> The module launches multiple kworkers which run Vector operations and
> verifies with scalar code. Also, the module provides userspace intefaces
> via fops to verify if we can run Vector code on syscall path.
Would it be contributed to kernel tools/testing/selftests/riscv/?
>
> Updated patches: 1, 2, 3, 4, 5
> New patches: -
> Unchanged patches: -
> Deleted patches: 6 (moved to 5)
>
> Changelog v2:
> - fix build issues
> - Follow arm's way of starting kernel-mode simd code:
> - add include/asm/simd.h and rename may_use_vector() ->
> may_use_simd()
> - return void in kernel_vector_begin(), and BUG_ON if may_use_simd()
> fails
> - Change naming scheme for functions/macros (Conor):
> - remove KMV
> - 's/rvv/vector/'
> - 's/RISCV_ISA_V_PREEMPTIVE_KMV/RISCV_ISA_V_PREEMPTIVE/'
> - 's/TIF_RISCV_V_KMV/TIF_RISCV_V_KERNEL_MODE/'
>
> Changes from the vector v12 series (for patch 2, 3):
> - return a failure code when kernel_vector_begin() fails.
> - Do not immediately restore user's V context.
>
> Andy Chiu (3):
> riscv: sched: defer restoring Vector context for user
> riscv: vector: do not pass task_struct into
> riscv_v_vstate_{save,restore}()
> riscv: vector: allow kernel-mode Vector with preemption
>
> Greentime Hu (2):
> riscv: Add support for kernel mode vector
> riscv: Add vector extension XOR implementation
>
> arch/riscv/Kconfig | 10 ++
> arch/riscv/include/asm/entry-common.h | 13 +++
> arch/riscv/include/asm/processor.h | 2 +
> arch/riscv/include/asm/simd.h | 52 +++++++++
> arch/riscv/include/asm/thread_info.h | 6 +
> arch/riscv/include/asm/vector.h | 50 +++++++--
> arch/riscv/include/asm/xor.h | 82 ++++++++++++++
> arch/riscv/kernel/Makefile | 1 +
> arch/riscv/kernel/asm-offsets.c | 2 +
> arch/riscv/kernel/entry.S | 45 ++++++++
> arch/riscv/kernel/kernel_mode_vector.c | 146 +++++++++++++++++++++++++
> arch/riscv/kernel/process.c | 10 +-
> arch/riscv/kernel/ptrace.c | 2 +-
> arch/riscv/kernel/signal.c | 4 +-
> arch/riscv/kernel/vector.c | 5 +-
> arch/riscv/lib/Makefile | 1 +
> arch/riscv/lib/xor.S | 81 ++++++++++++++
> 17 files changed, 495 insertions(+), 17 deletions(-)
> create mode 100644 arch/riscv/include/asm/simd.h
> create mode 100644 arch/riscv/include/asm/xor.h
> create mode 100644 arch/riscv/kernel/kernel_mode_vector.c
> create mode 100644 arch/riscv/lib/xor.S
>
> --
> 2.17.1
>
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2023-08-16 23:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 11:28 [v2, 0/5] riscv: support kernel-mode Vector Andy Chiu
2023-07-21 11:28 ` [v2, 1/5] riscv: sched: defer restoring Vector context for user Andy Chiu
2023-08-15 10:41 ` Björn Töpel
2023-07-21 11:28 ` [v2, 2/5] riscv: Add support for kernel mode vector Andy Chiu
2023-07-24 10:48 ` Conor Dooley
2023-07-24 15:48 ` Andy Chiu
2023-08-15 11:28 ` Björn Töpel
2023-08-16 23:36 ` Guo Ren
2023-07-21 11:28 ` [v2, 3/5] riscv: Add vector extension XOR implementation Andy Chiu
2023-07-24 10:51 ` Conor Dooley
2023-07-21 11:28 ` [v2, 4/5] riscv: vector: do not pass task_struct into riscv_v_vstate_{save,restore}() Andy Chiu
2023-07-21 11:28 ` [v2, 5/5] riscv: vector: allow kernel-mode Vector with preemption Andy Chiu
2023-07-24 12:18 ` Conor Dooley
2023-07-24 15:45 ` Andy Chiu
2023-07-24 16:26 ` Conor Dooley
2023-08-15 12:19 ` Björn Töpel
2023-08-16 23:18 ` Guo Ren [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=ZN1ZXcwYZtABNdUy@gmail.com \
--to=guoren@kernel.org \
--cc=andy.chiu@sifive.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@atishpatra.org \
--cc=bjorn@kernel.org \
--cc=greentime.hu@sifive.com \
--cc=guoren@linux.alibaba.com \
--cc=heiko.stuebner@vrull.eu \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=vineetg@rivosinc.com \
/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