From: Conor Dooley <conor.dooley@microchip.com>
To: Christoph Muellner <christoph.muellner@vrull.eu>
Cc: linux-riscv@lists.infradead.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Shuah Khan" <shuah@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Anup Patel" <apatel@ventanamicro.com>,
"Philipp Tomsich" <philipp.tomsich@vrull.eu>,
"Andrew Jones" <ajones@ventanamicro.com>,
"Guo Ren" <guoren@kernel.org>,
"Daniel Henrique Barboza" <dbarboza@ventanamicro.com>,
"Björn Töpel" <bjorn@rivosinc.com>,
"Alan Stern" <stern@rowland.harvard.edu>,
"Andrea Parri" <parri.andrea@gmail.com>,
"Will Deacon" <will@kernel.org>,
"Daniel Lustig" <dlustig@nvidia.com>,
"Peter Zijlstra" <peterz@infradead.org>
Subject: Re: [RFC PATCH 0/5] RISC-V: Add dynamic TSO support
Date: Mon, 27 Nov 2023 10:36:44 +0000 [thread overview]
Message-ID: <20231127-process-dinginess-cea6dd652b99@wendy> (raw)
In-Reply-To: <20231124072142.2786653-1-christoph.muellner@vrull.eu>
[-- Attachment #1: Type: text/plain, Size: 2066 bytes --]
Hi,
On Fri, Nov 24, 2023 at 08:21:37AM +0100, Christoph Muellner wrote:
> From: Christoph Müllner <christoph.muellner@vrull.eu>
>
> The upcoming RISC-V Ssdtso specification introduces a bit in the senvcfg
> CSR to switch the memory consistency model at run-time from RVWMO to TSO
> (and back). The active consistency model can therefore be switched on a
> per-hart base and managed by the kernel on a per-process/thread base.
>
> This patch implements basic Ssdtso support and adds a prctl API on top
> so that user-space processes can switch to a stronger memory consistency
> model (than the kernel was written for) at run-time.
>
> I am not sure if other architectures support switching the memory
> consistency model at run-time, but designing the prctl API in an
> arch-independent way allows reusing it in the future.
>
> The patchset also comes with a short documentation of the prctl API.
>
> This series is based on the second draft of the Ssdtso specification
> which was published recently on an RVI list:
> https://lists.riscv.org/g/tech-arch-review/message/183
> Note, that the Ssdtso specification is in development state
> (i.e., not frozen or even ratified) which is also the reason
> why I marked the series as RFC.
>
> One aspect that is not covered in this patchset is virtualization.
> It is planned to add virtualization support in a later version.
> Hints/suggestions on how to implement this part are very much
> appreciated.
>
> Christoph Müllner (5):
I know this is an RFC, but it could probably do with a bit more compile
testing, as:
> RISC-V: Add basic Ssdtso support
This patch doesn't build for rv64 allmodconfig
> RISC-V: Expose Ssdtso via hwprobe API
This one seems to build fine
> uapi: prctl: Add new prctl call to set/get the memory consistency
> model
> RISC-V: Implement prctl call to set/get the memory consistency model
> RISC-V: selftests: Add DTSO tests
These don't build for:
rv32 defconfig
rv64 allmodconfig
rv64 nommu
Cheers,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor.dooley@microchip.com>
To: Christoph Muellner <christoph.muellner@vrull.eu>
Cc: linux-riscv@lists.infradead.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Shuah Khan" <shuah@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Anup Patel" <apatel@ventanamicro.com>,
"Philipp Tomsich" <philipp.tomsich@vrull.eu>,
"Andrew Jones" <ajones@ventanamicro.com>,
"Guo Ren" <guoren@kernel.org>,
"Daniel Henrique Barboza" <dbarboza@ventanamicro.com>,
"Björn Töpel" <bjorn@rivosinc.com>,
"Alan Stern" <stern@rowland.harvard.edu>,
"Andrea Parri" <parri.andrea@gmail.com>,
"Will Deacon" <will@kernel.org>,
"Daniel Lustig" <dlustig@nvidia.com>,
"Peter Zijlstra" <peterz@infradead.org>
Subject: Re: [RFC PATCH 0/5] RISC-V: Add dynamic TSO support
Date: Mon, 27 Nov 2023 10:36:44 +0000 [thread overview]
Message-ID: <20231127-process-dinginess-cea6dd652b99@wendy> (raw)
In-Reply-To: <20231124072142.2786653-1-christoph.muellner@vrull.eu>
[-- Attachment #1.1: Type: text/plain, Size: 2066 bytes --]
Hi,
On Fri, Nov 24, 2023 at 08:21:37AM +0100, Christoph Muellner wrote:
> From: Christoph Müllner <christoph.muellner@vrull.eu>
>
> The upcoming RISC-V Ssdtso specification introduces a bit in the senvcfg
> CSR to switch the memory consistency model at run-time from RVWMO to TSO
> (and back). The active consistency model can therefore be switched on a
> per-hart base and managed by the kernel on a per-process/thread base.
>
> This patch implements basic Ssdtso support and adds a prctl API on top
> so that user-space processes can switch to a stronger memory consistency
> model (than the kernel was written for) at run-time.
>
> I am not sure if other architectures support switching the memory
> consistency model at run-time, but designing the prctl API in an
> arch-independent way allows reusing it in the future.
>
> The patchset also comes with a short documentation of the prctl API.
>
> This series is based on the second draft of the Ssdtso specification
> which was published recently on an RVI list:
> https://lists.riscv.org/g/tech-arch-review/message/183
> Note, that the Ssdtso specification is in development state
> (i.e., not frozen or even ratified) which is also the reason
> why I marked the series as RFC.
>
> One aspect that is not covered in this patchset is virtualization.
> It is planned to add virtualization support in a later version.
> Hints/suggestions on how to implement this part are very much
> appreciated.
>
> Christoph Müllner (5):
I know this is an RFC, but it could probably do with a bit more compile
testing, as:
> RISC-V: Add basic Ssdtso support
This patch doesn't build for rv64 allmodconfig
> RISC-V: Expose Ssdtso via hwprobe API
This one seems to build fine
> uapi: prctl: Add new prctl call to set/get the memory consistency
> model
> RISC-V: Implement prctl call to set/get the memory consistency model
> RISC-V: selftests: Add DTSO tests
These don't build for:
rv32 defconfig
rv64 allmodconfig
rv64 nommu
Cheers,
Conor.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-11-27 10:37 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 7:21 [RFC PATCH 0/5] RISC-V: Add dynamic TSO support Christoph Muellner
2023-11-24 7:21 ` Christoph Muellner
2023-11-24 7:21 ` [RFC PATCH 1/5] RISC-V: Add basic Ssdtso support Christoph Muellner
2023-11-24 7:21 ` Christoph Muellner
2023-11-24 7:21 ` [RFC PATCH 2/5] RISC-V: Expose Ssdtso via hwprobe API Christoph Muellner
2023-11-24 7:21 ` Christoph Muellner
2023-11-27 14:32 ` Samuel Holland
2023-11-27 14:32 ` Samuel Holland
2023-11-27 14:36 ` Christoph Müllner
2023-11-27 14:36 ` Christoph Müllner
2023-11-24 7:21 ` [RFC PATCH 3/5] uapi: prctl: Add new prctl call to set/get the memory consistency model Christoph Muellner
2023-11-24 7:21 ` Christoph Muellner
2023-11-24 15:41 ` kernel test robot
2023-11-24 15:42 ` kernel test robot
2023-11-24 15:42 ` kernel test robot
2023-11-24 7:21 ` [RFC PATCH 4/5] RISC-V: Implement " Christoph Muellner
2023-11-24 7:21 ` Christoph Muellner
2023-11-24 7:21 ` [RFC PATCH 5/5] RISC-V: selftests: Add DTSO tests Christoph Muellner
2023-11-24 7:21 ` Christoph Muellner
2023-11-24 10:15 ` [RFC PATCH 0/5] RISC-V: Add dynamic TSO support Peter Zijlstra
2023-11-24 10:15 ` Peter Zijlstra
2023-11-24 10:53 ` Christoph Müllner
2023-11-24 10:53 ` Christoph Müllner
2023-11-24 11:49 ` Peter Zijlstra
2023-11-24 11:49 ` Peter Zijlstra
[not found] ` <59da3e41-abb3-405a-8f98-c74bdf26935b@huaweicloud.com>
2023-11-24 11:54 ` Peter Zijlstra
2023-11-24 11:54 ` Peter Zijlstra
2023-11-24 13:05 ` Michael Ellerman
2023-11-24 13:05 ` Michael Ellerman
2023-11-26 12:34 ` Guo Ren
2023-11-26 12:34 ` Guo Ren
2023-11-27 12:14 ` Mark Rutland
2023-11-27 12:14 ` Mark Rutland
2024-02-08 11:10 ` Andrea Parri
2024-02-08 11:10 ` Andrea Parri
2023-11-25 2:51 ` Guo Ren
2023-11-25 2:51 ` Guo Ren
2023-11-27 11:16 ` Peter Zijlstra
2023-11-27 11:16 ` Peter Zijlstra
2023-11-28 1:42 ` Guo Ren
2023-11-28 1:42 ` Guo Ren
2023-11-27 10:36 ` Conor Dooley [this message]
2023-11-27 10:36 ` Conor Dooley
2023-11-27 12:58 ` Christoph Müllner
2023-11-27 12:58 ` Christoph Müllner
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=20231127-process-dinginess-cea6dd652b99@wendy \
--to=conor.dooley@microchip.com \
--cc=ajones@ventanamicro.com \
--cc=akpm@linux-foundation.org \
--cc=aou@eecs.berkeley.edu \
--cc=apatel@ventanamicro.com \
--cc=bjorn@rivosinc.com \
--cc=christoph.muellner@vrull.eu \
--cc=corbet@lwn.net \
--cc=dbarboza@ventanamicro.com \
--cc=dlustig@nvidia.com \
--cc=guoren@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=parri.andrea@gmail.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.org \
--cc=philipp.tomsich@vrull.eu \
--cc=shuah@kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=will@kernel.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.