From: Peter Zijlstra <peterz@infradead.org>
To: Jonas Oberhauser <jonas.oberhauser@huaweicloud.com>
Cc: "Christoph Muellner" <christoph.muellner@vrull.eu>,
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>,
"Conor Dooley" <conor.dooley@microchip.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>
Subject: Re: [RFC PATCH 0/5] RISC-V: Add dynamic TSO support
Date: Fri, 24 Nov 2023 12:54:30 +0100 [thread overview]
Message-ID: <20231124115430.GS3818@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <59da3e41-abb3-405a-8f98-c74bdf26935b@huaweicloud.com>
On Fri, Nov 24, 2023 at 12:04:09PM +0100, Jonas Oberhauser wrote:
> > I think ARM64 approached this problem by adding the
> > load-acquire/store-release instructions and for TSO based code,
> > translate into those (eg. x86 -> arm64 transpilers).
>
>
> Although those instructions have a bit more ordering constraints.
>
> I have heard rumors that the apple chips also have a register that can be
> set at runtime.
Oh, I thought they made do with the load-acquire/store-release thingies.
But to be fair, I haven't been paying *that* much attention to the apple
stuff.
I did read about how they fudged some of the x86 flags thing.
> And there are some IBM machines that have a setting, but not sure how it is
> controlled.
Cute, I'm assuming this is the Power series (s390 already being TSO)? I
wasn't aware they had this.
> > IIRC Risc-V actually has such instructions as well, so *why* are you
> > doing this?!?!
>
>
> Unfortunately, at least last time I checked RISC-V still hadn't gotten such
> instructions.
> What they have is the *semantics* of the instructions, but no actual opcodes
> to encode them.
Well, that sucks..
> I argued for them in the RISC-V memory group, but it was considered to be
> outside the scope of that group.
>
> Transpiling with sufficient DMB ISH to get the desired ordering is really
> bad for performance.
Ha!, quite dreadful I would imagine.
> That is not to say that linux should support this. Perhaps linux should
> pressure RISC-V into supporting implicit barriers instead.
I'm not sure I count for much in this regard, but yeah, that sounds like
a plan :-)
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Jonas Oberhauser <jonas.oberhauser@huaweicloud.com>
Cc: "Christoph Muellner" <christoph.muellner@vrull.eu>,
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>,
"Conor Dooley" <conor.dooley@microchip.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>
Subject: Re: [RFC PATCH 0/5] RISC-V: Add dynamic TSO support
Date: Fri, 24 Nov 2023 12:54:30 +0100 [thread overview]
Message-ID: <20231124115430.GS3818@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <59da3e41-abb3-405a-8f98-c74bdf26935b@huaweicloud.com>
On Fri, Nov 24, 2023 at 12:04:09PM +0100, Jonas Oberhauser wrote:
> > I think ARM64 approached this problem by adding the
> > load-acquire/store-release instructions and for TSO based code,
> > translate into those (eg. x86 -> arm64 transpilers).
>
>
> Although those instructions have a bit more ordering constraints.
>
> I have heard rumors that the apple chips also have a register that can be
> set at runtime.
Oh, I thought they made do with the load-acquire/store-release thingies.
But to be fair, I haven't been paying *that* much attention to the apple
stuff.
I did read about how they fudged some of the x86 flags thing.
> And there are some IBM machines that have a setting, but not sure how it is
> controlled.
Cute, I'm assuming this is the Power series (s390 already being TSO)? I
wasn't aware they had this.
> > IIRC Risc-V actually has such instructions as well, so *why* are you
> > doing this?!?!
>
>
> Unfortunately, at least last time I checked RISC-V still hadn't gotten such
> instructions.
> What they have is the *semantics* of the instructions, but no actual opcodes
> to encode them.
Well, that sucks..
> I argued for them in the RISC-V memory group, but it was considered to be
> outside the scope of that group.
>
> Transpiling with sufficient DMB ISH to get the desired ordering is really
> bad for performance.
Ha!, quite dreadful I would imagine.
> That is not to say that linux should support this. Perhaps linux should
> pressure RISC-V into supporting implicit barriers instead.
I'm not sure I count for much in this regard, but yeah, that sounds like
a plan :-)
_______________________________________________
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-24 11:55 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
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
[not found] ` <59da3e41-abb3-405a-8f98-c74bdf26935b@huaweicloud.com>
2023-11-24 11:54 ` Peter Zijlstra [this message]
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-27 10:36 ` Conor Dooley
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=20231124115430.GS3818@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--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=conor.dooley@microchip.com \
--cc=corbet@lwn.net \
--cc=dbarboza@ventanamicro.com \
--cc=dlustig@nvidia.com \
--cc=guoren@kernel.org \
--cc=jonas.oberhauser@huaweicloud.com \
--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=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.