From: Mayuresh Chitale <mchitale@ventanamicro.com>
To: palmer@dabbelt.com, aou@eecs.berkeley.edu, paul.walmsley@sifive.com
Cc: anup@brainfault.org, atishp@rivosinc.com,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
Mayuresh Chitale <mchitale@ventanamicro.com>
Subject: [RFC PATCH 0/2] Risc-V Svinval support
Date: Wed, 16 Feb 2022 10:51:08 +0530 [thread overview]
Message-ID: <20220216052110.1053665-1-mchitale@ventanamicro.com> (raw)
This patch adds support for the Svinval extension version 1.0 as defined in the
Risc V Privileged specification. It depends on and needs to be applied on the
following patchsets from Atish and Anup respectively:
https://patchwork.kernel.org/project/linux-riscv/list/?series=613234
https://patchwork.kernel.org/project/linux-riscv/list/?series=609361
The feature was tested with qemu from latest staging branch with following
additional patch:
https://lists.nongnu.org/archive/html/qemu-riscv/2022-02/msg00100.html
Mayuresh Chitale (2):
riscv: enum for svinval extension
riscv: mm: use svinval instructions instead of sfence.vma
arch/riscv/include/asm/hwcap.h | 1 +
arch/riscv/include/asm/tlbflush.h | 14 +++++++
arch/riscv/kernel/cpu.c | 1 +
arch/riscv/kernel/setup.c | 1 +
arch/riscv/mm/Makefile | 1 +
arch/riscv/mm/tlb.S | 53 +++++++++++++++++++++++
arch/riscv/mm/tlbflush.c | 70 ++++++++++++++++++++++++++++---
7 files changed, 135 insertions(+), 6 deletions(-)
create mode 100644 arch/riscv/mm/tlb.S
--
2.25.1
next reply other threads:[~2022-02-16 5:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 5:21 Mayuresh Chitale [this message]
2022-02-16 5:21 ` [RFC PATCH 1/2] riscv: enum for svinval extension Mayuresh Chitale
2022-02-28 13:09 ` Anup Patel
2022-02-16 5:21 ` [RFC PATCH 2/2] riscv: mm: use svinval instructions instead of sfence.vma Mayuresh Chitale
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=20220216052110.1053665-1-mchitale@ventanamicro.com \
--to=mchitale@ventanamicro.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@rivosinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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