public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Tsukasa OI <research_trasio@irq.a4lg.com>
Cc: binutils@sourceware.org
Subject: [REVIEW ONLY 0/1] UNRATIFIED RISC-V: Add 'Svadu' extension
Date: Tue, 29 Nov 2022 01:18:14 +0000	[thread overview]
Message-ID: <cover.1669684692.git.research_trasio@irq.a4lg.com> (raw)

*** WAIT FOR SPECIFICATION FREEZE ***
This is an implementation for unratified and not frozen RISC-V extension
and not intended to be merged for now.
The only intent to submit this patchset is to test new instructions for
your (possibly virtual) environment and early review for fast adoption
after ratification.


This patchset adds following unratified extension to GNU Binutils:

-   'Svadu' (Hardware Updating of PTE A/D Bits)
    version 0.1 (may change on ratification)

which adds no instructions or no CSRs (but new CSR bits so 'Zicsr'
dependency is added along with extension name support).

This extension provides CSR-based control of hardware PTE updates.


This is based on the specification documentation, version 0.1:
<https://github.com/riscv/riscv-svadu/releases/tag/vv0.1>




Tsukasa OI (1):
  UNRATIFIED RISC-V: Add 'Svadu' extension

 bfd/elfxx-riscv.c | 2 ++
 1 file changed, 2 insertions(+)


base-commit: cb44f89ce977b1ab2d4063f2487950bddfb75bc7
-- 
2.38.1


             reply	other threads:[~2022-11-29  1:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29  1:18 Tsukasa OI [this message]
2022-11-29  1:18 ` [REVIEW ONLY 1/1] " Tsukasa OI
2022-11-29  1:57   ` Palmer Dabbelt
2023-09-03  3:13 ` [REVIEW ONLY 0/1] RISC-V: Add stub support for the " Tsukasa OI
2023-09-03  3:13   ` [REVIEW ONLY 1/1] " Tsukasa OI
2023-09-03  3:16   ` [REVIEW ONLY 0/1] " Tsukasa OI
2023-09-05  6:55     ` Nelson Chu

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=cover.1669684692.git.research_trasio@irq.a4lg.com \
    --to=research_trasio@irq.a4lg.com \
    --cc=binutils@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).