From: Jeff Xu <jeffxu@chromium.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
edumazet@google.com, m-malladi@ti.com,
Kevin Brodsky <kevin.brodsky@arm.com>,
guoweikang.kernel@gmail.com,
Qi Zheng <zhengqi.arch@bytedance.com>
Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
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: Tue, 18 Mar 2025 11:39:21 -0700 [thread overview]
Message-ID: <CABi2SkUAnWAu9L-Km35U4XMmbp9-w+hKCXkM6MYNejYi5ip5Tg@mail.gmail.com> (raw)
In-Reply-To: <CABi2SkVndMyOUpRR8z7f0J-r7chkVNZ17-kaEcBje1kBjk-1iw@mail.gmail.com>
Hi Geert
On Tue, Mar 18, 2025 at 10:21 AM Jeff Xu <jeffxu@chromium.org> wrote:
>
> Hi Geert,
>
> On Mon, Mar 17, 2025 at 12:14 PM Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
> >
> > Hi Jeff,
> >
> > On Mon, 17 Mar 2025 at 20:02, Jeff Xu <jeffxu@chromium.org> wrote:
> > > 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:
> > > > > 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.
> >
> > That way you only find users of the symbol, not where it is defined.
> >
> > You can use
> >
> > git grep -W "config\s*64BIT" -- arch/
> >
> > to find out which architectures are 32-bit, 64-bit, or support both.
> >
Microblaze, openrisc, sh, hexagon all don't have CONFIG 64BIT defined
in KCONFIG, and are not using CONFIG_64BIT in their arch code. Is
there something else that makes you point out the hexagon as 32 bit
only (and not other 3) ?
The microblaze/ openrisc/sh are currently listed as TODO in this patch
, and that is because the search results show they have 64 bits CPU.
But I like to double check.
I included some people who recently merged into those arches in case
anyone is familiar with 32bit/64 bits usage in those architectures.
Thanks
-Jeff
> Good to know, thanks!
>
> > > > > > > > --- /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.
> >
> > Alpha is 64-bit only. So the code under arch/alpha/ does not need to check for
> > CONFIG_64BIT, hence you didn't find it;-)
> >
> > > > > > > > + | 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.
> >
> > 32-bit only on Linux.
> >
> Ok. Thank you for correcting this.
>
> 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
next prev parent reply other threads:[~2025-03-18 18:39 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
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 [this message]
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=CABi2SkUAnWAu9L-Km35U4XMmbp9-w+hKCXkM6MYNejYi5ip5Tg@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=edumazet@google.com \
--cc=geert@linux-m68k.org \
--cc=gor@linux.ibm.com \
--cc=guoweikang.kernel@gmail.com \
--cc=hca@linux.ibm.com \
--cc=kees@kernel.org \
--cc=kevin.brodsky@arm.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=m-malladi@ti.com \
--cc=svens@linux.ibm.com \
--cc=thomas.weissschuh@linutronix.de \
--cc=zhengqi.arch@bytedance.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