From: Jeff Xu <jeffxu@chromium.org>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: akpm@linux-foundation.org, Liam.Howlett@oracle.com,
agordeev@linux.ibm.com, borntraeger@linux.ibm.com,
gor@linux.ibm.com, hca@linux.ibm.com, kees@kernel.org,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, svens@linux.ibm.com,
thomas.weissschuh@linutronix.de
Subject: Re: [PATCH] mseal sysmap: add arch-support txt
Date: Thu, 13 Mar 2025 15:25:46 -0700 [thread overview]
Message-ID: <CABi2SkVKxyX0uDabg+wHiq_vTBFbUST-nRdur7cCPB2myhCWhg@mail.gmail.com> (raw)
In-Reply-To: <1bbce89c-1efe-40cf-9085-ec4ec16f7996@lucifer.local>
On Wed, Mar 12, 2025 at 10:21 PM Lorenzo Stoakes
<lorenzo.stoakes@oracle.com> wrote:
>
> On Thu, Mar 13, 2025 at 12:06:23AM +0000, jeffxu@chromium.org wrote:
> > From: Jeff Xu <jeffxu@chromium.org>
> >
> > Add Documentation/features/core/mseal_sys_mappings/arch-support.txt
> >
> > Signed-off-by: Jeff Xu <jeffxu@chromium.org>
> > ---
> > .../core/mseal_sys_mappings/arch-support.txt | 30 +++++++++++++++++++
> > 1 file changed, 30 insertions(+)
> > create mode 100644 Documentation/features/core/mseal_sys_mappings/arch-support.txt
> >
> > diff --git a/Documentation/features/core/mseal_sys_mappings/arch-support.txt b/Documentation/features/core/mseal_sys_mappings/arch-support.txt
> > new file mode 100644
> > index 000000000000..8db637254de9
> > --- /dev/null
> > +++ b/Documentation/features/core/mseal_sys_mappings/arch-support.txt
> > @@ -0,0 +1,30 @@
> > +#
> > +# Feature name: mseal-system-mappings
> > +# Kconfig: ARCH_SUPPORTS_MSEAL_SYSTEM_MAPPINGS
> > +# description: arch supports mseal system mappings
> > +#
> > + -----------------------
> > + | arch |status|
> > + -----------------------
> > + | alpha: | TODO |
> > + | arc: | TODO |
> > + | arm: | N/A |
> > + | arm64: | ok |
> > + | csky: | TODO |
> > + | hexagon: | TODO |
> > + | loongarch: | TODO |
> > + | m68k: | TODO |
> > + | microblaze: | TODO |
> > + | mips: | TODO |
> > + | nios2: | TODO |
> > + | openrisc: | TODO |
> > + | parisc: | TODO |
> > + | powerpc: | TODO |
> > + | riscv: | TODO |
> > + | s390: | ok |
> > + | sh: | TODO |
> > + | sparc: | TODO |
> > + | um: | TODO |
> > + | x86: | ok |
> > + | xtensa: | TODO |
> > + -----------------------
> > --
> > 2.49.0.rc0.332.g42c0ae87b1-goog
> >
>
> I mean fine, but why not in the existing mseal documentation file where you
> already document system mappings?
>
you mean adding s390 in the mseal.rst ? I thought Heiko was going to
add that ? [1], maybe not ?
From the example given by Heiko [1] , arch-support.txt is the official
way of documenting arch specific support. But adding these info in
mseal.rst won't hurt.
> Plus I feel this need expansion a bit 'N/A' is because of being non-64 bit
> right?
>
Below is the definition of N/A in Documentation/features/arch-support.txt
| N/A| # feature doesn't apply to the architecture
It fits the arm case because mseal is not supported in 32 bit.
> Actually this will change soon btw, based on Matthew's idea I plan to drop the
> 32-bit vma flags limit.
>
Okay, we can update this section to TODO when 32-bit vma flags are
expanded. Based on past comments, I gather we want the document to
reflect the current state of the kernel, not future features.
> Anyway yeah, let's move that over there please.
I'm looking at Heiko's direction first to see if mseal.rst will be
updated as part of the s390 patch, technically that belongs to Heiko's
patch series. I can also add that if Heiko doesn't care :-)
Thanks
-Jeff
[1]https://lore.kernel.org/all/20250312153946.10610B02-hca@linux.ibm.com/
next prev parent reply other threads:[~2025-03-13 22:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 0:06 jeffxu
2025-03-13 5:21 ` Lorenzo Stoakes
2025-03-13 22:25 ` Jeff Xu [this message]
2025-03-14 10:41 ` Geert Uytterhoeven
2025-03-17 18:14 ` Jeff Xu
2025-03-17 19:02 ` Jeff Xu
2025-03-17 19:14 ` Geert Uytterhoeven
2025-03-18 17:21 ` Jeff Xu
2025-03-18 18:39 ` Jeff Xu
2025-03-19 8:17 ` Geert Uytterhoeven
2025-03-19 16:56 ` Jeff Xu
2025-03-17 13:22 ` Heiko Carstens
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=CABi2SkVKxyX0uDabg+wHiq_vTBFbUST-nRdur7cCPB2myhCWhg@mail.gmail.com \
--to=jeffxu@chromium.org \
--cc=Liam.Howlett@oracle.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=svens@linux.ibm.com \
--cc=thomas.weissschuh@linutronix.de \
/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