Re: [PATCH] mseal sysmap: add arch-support txt

[Jeff Xu <jeffxu@chromium.org>]

On Mon, Mar 17, 2025 at 11:14 AM Jeff Xu <jeffxu@chromium.org> wrote:
>
> On Fri, Mar 14, 2025 at 3:41 AM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> >
> > Hi Jeff,
> >
> > On Thu, 13 Mar 2025 at 23:26, Jeff Xu <jeffxu@chromium.org> wrote:
> > > 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>
> >
> > Thanks for your patch!
> >

I used "find * |xargs grep -i  CONFIG_64BIT" to look for CONFIG_64BIT
under arch/, and together with internet search/wiki page, and below is
the proposed update.

> > > > > --- /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 |
No CONFIG_64BIT found under arch/alpha, but search results show alpha
supports 64 bits. Keep as TODO.

> > > > > +    |         arc: | TODO |
> > > > > +    |         arm: |  N/A |
> > > > > +    |       arm64: |  ok  |
> > > > > +    |        csky: | TODO |
(N/A)

> > > > > +    |     hexagon: | TODO |
No CONFIG_64BIT found under arch/hexagon, but search results show
hexagon supports 64 bits. Keep as TODO.

> > > > > +    |   loongarch: | TODO |
> > > > > +    |        m68k: | TODO |
(N/A)

> > > > > +    |  microblaze: | TODO |
No CONFIG_64BIT found under arch/microblaze, but search results show
microblaze supports both 32 and 64 bits. Keep as TODO.

> > > > > +    |        mips: | TODO |
> > > > > +    |       nios2: | TODO |
(N/A)

> > > > > +    |    openrisc: | TODO |
No CONFIG_64BIT found under arch/openrisc, but search results show
microblaze supports both 32 and 64 bits. Keep as TODO.

> > > > > +    |      parisc: | TODO |
> > > > > +    |     powerpc: | TODO |
> > > > > +    |       riscv: | TODO |
> > > > > +    |        s390: |  ok  |
> > > > > +    |          sh: | TODO |
No CONFIG_64BIT found under arch/openrisc, but wikipedia shows sh-5 is
a 64 bit, so Keep as TODO.

> > > > > +    |       sparc: | TODO |
> > > > > +    |          um: | TODO |
> > > > > +    |         x86: |  ok  |
> > > > > +    |      xtensa: | TODO |
N/A

In summary: csky, m68k, nios2, xtensa, arm only have a 32 bit CPU and
will use "N/A".
I will leave it open for a while, If no objection , I will send a new
patch version.

Thanks.
-Jeff

> > > > > +    -----------------------
> >
> > > > 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.
> >
> > IIUIC, you can already s@TODO@N/A@ for all other 32-bit architectures,
> > so we don't accidentally spend time on looking into adding the support?
> >
> Sure, my architecture knowledge is limited.
>
> I just checked this, it seems to me that csky, m68k, nios2, sh, xtensa
> doesn't have 64 bits support, the rest have 64 bits. Is this correct ?
>



> Thanks
> -Jeff
>
>
>
> > Gr{oetje,eeting}s,
> >
> >                         Geert
> >
> > --
> > Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
> >
> > In personal conversations with technical people, I call myself a hacker. But
> > when I'm talking to journalists I just say "programmer" or something like that.
> >                                 -- Linus Torvalds