[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CABi2SkX2piCzCHMoxe5txGCZ0wAkMbZ0A1VeMottZo5xa3-A-A@mail.gmail.com>
Date: Wed, 19 Mar 2025 09:56:28 -0700
From: Jeff Xu <jeffxu@...omium.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: edumazet@...gle.com, m-malladi@...com,
Kevin Brodsky <kevin.brodsky@....com>, guoweikang.kernel@...il.com,
Qi Zheng <zhengqi.arch@...edance.com>, Lorenzo Stoakes <lorenzo.stoakes@...cle.com>,
akpm@...ux-foundation.org, Liam.Howlett@...cle.com, agordeev@...ux.ibm.com,
borntraeger@...ux.ibm.com, gor@...ux.ibm.com, hca@...ux.ibm.com,
kees@...nel.org, linux-hardening@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org, svens@...ux.ibm.com,
thomas.weissschuh@...utronix.de
Subject: Re: [PATCH] mseal sysmap: add arch-support txt
Hi Geert
On Wed, Mar 19, 2025 at 1:17 AM Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
>
> Hi Jeff,
>
> On Tue, 18 Mar 2025 at 19:39, Jeff Xu <jeffxu@...omium.org> wrote:
> > On Tue, Mar 18, 2025 at 10:21 AM Jeff Xu <jeffxu@...omium.org> wrote:
> > > On Mon, Mar 17, 2025 at 12:14 PM Geert Uytterhoeven
> > > <geert@...ux-m68k.org> wrote:
> > > > On Mon, 17 Mar 2025 at 20:02, Jeff Xu <jeffxu@...omium.org> wrote:
> > > > > On Mon, Mar 17, 2025 at 11:14 AM Jeff Xu <jeffxu@...omium.org> wrote:
> > > > > > On Fri, Mar 14, 2025 at 3:41 AM Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
> > > > > > > On Thu, 13 Mar 2025 at 23:26, Jeff Xu <jeffxu@...omium.org> wrote:
> > > > > > > > On Wed, Mar 12, 2025 at 10:21 PM Lorenzo Stoakes
> > > > > > > > <lorenzo.stoakes@...cle.com> wrote:
> > > > > > > > > On Thu, Mar 13, 2025 at 12:06:23AM +0000, jeffxu@...omium.org wrote:
> > > > > > > > > > From: Jeff Xu <jeffxu@...omium.org>
> > > > > > > > > > Add Documentation/features/core/mseal_sys_mappings/arch-support.txt
> > > > > > > > > >
> > > > > > > > > > Signed-off-by: Jeff Xu <jeffxu@...omium.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) ?
>
> AFAIK Microblaze, openrisc, and hexagon are all 32-bit.
> Linux used to support sh64, but that was dropped, as sh64 never went
> beyond prototype hardware.
>
Great ! Thanks for the information.
I will update accordingly.
-Jeff
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-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
Powered by blists - more mailing lists