From: Charlie Jenkins <charlie@rivosinc.com>
To: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Andrea Parri <parri.andrea@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
Charlie Jenkins <charlie@rivosinc.com>
Subject: [PATCH v2 0/2] tools: Add barrier implementations for riscv
Date: Tue, 06 Aug 2024 15:01:22 -0700 [thread overview]
Message-ID: <20240806-optimize_ring_buffer_read_riscv-v2-0-ca7e193ae198@rivosinc.com> (raw)
Add support for riscv specific barrier implementations to the tools
tree, so that fence instructions can be emitted for synchronization.
Signed-off-by: Charlie Jenkins <charlie@rivosinc.com>
---
Changes in v2:
- Fix typo in commit message
- Link to v1: https://lore.kernel.org/r/20240729-optimize_ring_buffer_read_riscv-v1-0-6bbc0f2434ee@rivosinc.com
---
Charlie Jenkins (2):
tools: Add riscv barrier implementation
tools: Optimize ring buffer for riscv
tools/arch/riscv/include/asm/barrier.h | 39 ++++++++++++++++++++++++++++++++++
tools/arch/riscv/include/asm/fence.h | 13 ++++++++++++
tools/include/asm/barrier.h | 2 ++
tools/include/linux/ring_buffer.h | 2 +-
4 files changed, 55 insertions(+), 1 deletion(-)
---
base-commit: 0c3836482481200ead7b416ca80c68a29cfdaabd
change-id: 20240725-optimize_ring_buffer_read_riscv-228491c4eb6e
--
- Charlie
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2024-08-06 22:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 22:01 Charlie Jenkins [this message]
2024-08-06 22:01 ` [PATCH v2 1/2] tools: Add riscv barrier implementation Charlie Jenkins
2024-10-01 9:20 ` Andreas Schwab
2024-08-06 22:01 ` [PATCH v2 2/2] tools: Optimize ring buffer for riscv Charlie Jenkins
2024-09-24 6:40 ` [PATCH v2 0/2] tools: Add barrier implementations " patchwork-bot+linux-riscv
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=20240806-optimize_ring_buffer_read_riscv-v2-0-ca7e193ae198@rivosinc.com \
--to=charlie@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=parri.andrea@gmail.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