[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdX2-dTkRcDJGszH7cuZCDO-ZSq4n50R9-+p2s9=P5AzKA@mail.gmail.com>
Date: Fri, 6 Dec 2024 09:03:32 +0100
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Zi Yan <ziy@...dia.com>
Cc: David Hildenbrand <david@...hat.com>, Matthew Wilcox <willy@...radead.org>,
Vlastimil Babka <vbabka@...e.cz>, linux-mm@...ck.org,
Andrew Morton <akpm@...ux-foundation.org>, Miaohe Lin <linmiaohe@...wei.com>,
Kefeng Wang <wangkefeng.wang@...wei.com>, John Hubbard <jhubbard@...dia.com>,
"Huang, Ying" <ying.huang@...el.com>, Ryan Roberts <ryan.roberts@....com>,
Alexander Potapenko <glider@...gle.com>, Kees Cook <keescook@...omium.org>, linux-kernel@...r.kernel.org,
linux-mips@...r.kernel.org
Subject: Re: [PATCH] mm: avoid zeroing user movable page twice with init_on_alloc=1
Hi Zi,
On Thu, Dec 5, 2024 at 5:05 PM Zi Yan <ziy@...dia.com> wrote:
> Is it possible to run a 32bit kernel with HIGHMEM and
> CONFIG_INIT_ON_ALLOC_DEFAULT_ON on the machine (of course with my patch
> reverted)? Just to check my reasoning below.
While I can boot 32-bit kernels, CPU_TX49XX and MACH_TX49XX do not
select CPU_SUPPORTS_HIGHMEM resp. SYS_SUPPORTS_HIGHMEM, and thus
HIGHMEM is not supported.
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