From: Andrew Jones <ajones@ventanamicro.com>
To: Samuel Holland <samuel.holland@sifive.com>
Cc: linux-riscv@lists.infradead.org,
Palmer Dabbelt <palmer@dabbelt.com>,
Conor Dooley <conor@kernel.org>,
linux-kernel@vger.kernel.org, Deepak Gupta <debug@rivosinc.com>
Subject: Re: [PATCH v2 0/3] riscv: Per-thread envcfg CSR support
Date: Fri, 21 Jun 2024 14:54:43 +0200 [thread overview]
Message-ID: <20240621-368af6395900f29559358915@orel> (raw)
In-Reply-To: <20240613171447.3176616-1-samuel.holland@sifive.com>
On Thu, Jun 13, 2024 at 10:14:38AM GMT, Samuel Holland wrote:
> This series (or equivalent) is a prerequisite for both user-mode pointer
> masking and CFI support, as those are per-thread features are controlled
> by fields in the envcfg CSR. These patches are based on v1 of the
> pointer masking series[1], with significant input from both Deepak and
> Andrew. By sending this as a separate series, hopefully we can converge
> on a single implementation of this functionality.
>
> [1]: https://lore.kernel.org/linux-riscv/20240319215915.832127-6-samuel.holland@sifive.com/
>
> Changes in v2:
> - Rebase on riscv/linux.git for-next
>
> Samuel Holland (3):
> riscv: Enable cbo.zero only when all harts support Zicboz
> riscv: Add support for per-thread envcfg CSR values
> riscv: Call riscv_user_isa_enable() only on the boot hart
>
For the series,
Reviewed-by: Andrew Jones <ajones@ventanamicro.com>
Thanks,
drew
prev parent reply other threads:[~2024-06-21 12:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 17:14 Samuel Holland
2024-06-13 17:14 ` [PATCH v2 1/3] riscv: Enable cbo.zero only when all harts support Zicboz Samuel Holland
2024-06-14 10:31 ` Conor Dooley
2024-06-13 17:14 ` [PATCH v2 2/3] riscv: Add support for per-thread envcfg CSR values Samuel Holland
2024-06-13 17:14 ` [PATCH v2 3/3] riscv: Call riscv_user_isa_enable() only on the boot hart Samuel Holland
2024-06-14 10:32 ` Conor Dooley
2024-06-21 12:54 ` Andrew Jones [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=20240621-368af6395900f29559358915@orel \
--to=ajones@ventanamicro.com \
--cc=conor@kernel.org \
--cc=debug@rivosinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=samuel.holland@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
all inboxes | Powered by JetHome®