From: Palmer Dabbelt <palmer@rivosinc.com>
To: linux-riscv@lists.infradead.org
Cc: Palmer Dabbelt <palmer@rivosinc.com>
Subject: [PATCH] Documentation: RISC-V: Define Xlinuxs{s,m}aia
Date: Thu, 2 Feb 2023 16:12:01 -0800 [thread overview]
Message-ID: <20230203001201.14770-1-palmer@rivosinc.com> (raw)
The AIA specification was only partially frozen, but provides no way to
refer to the subset of behavior that has been frozen. It seems like
there's not a whole lot of interest in the non-frozen behavior, so let's
just define an extension that only consists of the frozen behavior
Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
---
Documentation/riscv/extensions.rst | 10 ++++++++++
1 file changed, 10 insertions(+)
create mode 100644 Documentation/riscv/extensions.rst
diff --git a/Documentation/riscv/extensions.rst b/Documentation/riscv/extensions.rst
new file mode 100644
index 000000000000..c12bd3780520
--- /dev/null
+++ b/Documentation/riscv/extensions.rst
@@ -0,0 +1,10 @@
+.. SPDX-License-Identifier: GPL-2.0
+
+Custom RISC-V Extensions
+========================
+
+* The `Xlinuxsmaia` and `Xlinuxssaia` extensions coorespond to the standard
+ `Smaia` and `Ssaia` extensions as defined by version 1.0-RC2 of the RISC-V
+ Advanced Interrupt Architecture (AIA) specification, with the difference that
+ chapters 5 (Duo-PLIC) and 9 (IOMMU Support for MSIs to Virtual Machines) do
+ not exist.
--
2.39.0
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2023-02-03 0:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 0:12 Palmer Dabbelt [this message]
2023-02-03 7:32 ` [PATCH] Documentation: RISC-V: Define Xlinuxs{s,m}aia Conor Dooley
2023-02-08 15:52 ` Palmer Dabbelt
2023-02-08 16:07 ` Conor Dooley
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=20230203001201.14770-1-palmer@rivosinc.com \
--to=palmer@rivosinc.com \
--cc=linux-riscv@lists.infradead.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.