loongarch.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Huacai Chen <chenhuacai@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Huacai Chen <chenhuacai@loongson.cn>,
	loongarch@lists.linux.dev,  Xuefeng Li <lixuefeng@loongson.cn>,
	guoren <guoren@kernel.org>,  WANG Xuerui <kernel@xen0n.name>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH V4 14/14] LoongArch: Adjust build infrastructure for 32BIT/64BIT
Date: Fri, 28 Nov 2025 22:27:48 +0800	[thread overview]
Message-ID: <CAAhV-H40yf7Sb=x0muVT_DCg9D6YcEDTsfxY4kRQLHt0N5JYSw@mail.gmail.com> (raw)
In-Reply-To: <12520d82-d858-4067-b9ef-baddb596ee56@app.fastmail.com>

On Fri, Nov 28, 2025 at 9:57 PM Arnd Bergmann <arnd@arndb.de> wrote:
>
> On Thu, Nov 27, 2025, at 16:48, Huacai Chen wrote:
> >
> > +config 4KB_2LEVEL
> > +     bool "4KB with 2 levels"
> > +     select HAVE_PAGE_SIZE_4KB
> > +     select PGTABLE_2LEVEL
> > +     help
> > +       This option selects 16KB page size with 2 level page tables, which
> > +       support a maximum of 32 bits of application virtual memory.
> > +
>
> I just noticed this inconsistency: the text says 16KB pages, the
> option says 4KB, so one of them is wrong. Usually 4KB pages have
> a 32-bit address space (using 32-bit descriptors), so I assume
> this one is correct.
Yes, 4KB is correct, thank you for pointing out.

Huacai
>
>       arnd
>

  reply	other threads:[~2025-11-28 14:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-27 15:48 [PATCH V4 00/14] LoongArch: Add basic LoongArch32 support Huacai Chen
2025-11-27 15:48 ` [PATCH V4 01/14] LoongArch: Add atomic operations for 32BIT/64BIT Huacai Chen
2025-11-27 15:48 ` [PATCH V4 02/14] LoongArch: Add adaptive CSR accessors " Huacai Chen
2025-11-27 15:48 ` [PATCH V4 03/14] LoongArch: Adjust common macro definitions " Huacai Chen
2025-11-27 15:48 ` [PATCH V4 04/14] LoongArch: Adjust boot & setup " Huacai Chen
2025-11-27 15:48 ` [PATCH V4 05/14] LoongArch: Adjust memory management " Huacai Chen
2025-11-27 15:48 ` [PATCH V4 06/14] LoongArch: Adjust process " Huacai Chen
2025-11-27 15:48 ` [PATCH V4 07/14] LoongArch: Adjust time routines " Huacai Chen
2025-11-27 15:48 ` [PATCH V4 08/14] LoongArch: Adjust module loader " Huacai Chen
2025-11-27 15:48 ` [PATCH V4 09/14] LoongArch: Adjust system call " Huacai Chen
2025-11-27 15:48 ` [PATCH V4 10/14] LoongArch: Adjust user accessors " Huacai Chen
2025-11-27 15:48 ` [PATCH V4 11/14] LoongArch: Adjust misc routines " Huacai Chen
2025-11-27 15:48 ` [PATCH V4 12/14] LoongArch: Adjust VDSO/VSYSCALL " Huacai Chen
2025-11-27 15:48 ` [PATCH V4 13/14] LoongArch: Adjust default config files " Huacai Chen
2025-11-27 15:48 ` [PATCH V4 14/14] LoongArch: Adjust build infrastructure " Huacai Chen
2025-11-28 13:57   ` Arnd Bergmann
2025-11-28 14:27     ` Huacai Chen [this message]
2026-04-23 22:06   ` Nathan Chancellor
2026-04-24  4:14     ` Huacai Chen
2026-04-24 11:06     ` WANG Rui
2026-04-24 18:19       ` Nathan Chancellor
2026-04-25  2:29         ` hev

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='CAAhV-H40yf7Sb=x0muVT_DCg9D6YcEDTsfxY4kRQLHt0N5JYSw@mail.gmail.com' \
    --to=chenhuacai@kernel.org \
    --cc=arnd@arndb.de \
    --cc=chenhuacai@loongson.cn \
    --cc=guoren@kernel.org \
    --cc=jiaxun.yang@flygoat.com \
    --cc=kernel@xen0n.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lixuefeng@loongson.cn \
    --cc=loongarch@lists.linux.dev \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).