[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7e89f00b-0b7a-4ef6-90e6-bb5f1b7946e2@amperemail.onmicrosoft.com>
Date: Tue, 10 Dec 2024 11:22:09 +0800
From: Shijie Huang <shijie@...eremail.onmicrosoft.com>
To: "Christoph Lameter (Ampere)" <cl@...two.org>,
Huang Shijie <shijie@...amperecomputing.com>
Cc: catalin.marinas@....com, will@...nel.org, anshuman.khandual@....com,
corbet@....net, patches@...erecomputing.com, akpm@...ux-foundation.org,
thuth@...hat.com, rostedt@...dmis.org, xiongwei.song@...driver.com,
ardb@...nel.org, inux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v3 1/2] arm64: refactor the rodata=xxx
On 2024/12/10 1:05, Christoph Lameter (Ampere) wrote:
>> --- a/Documentation/admin-guide/kernel-parameters.txt
>> +++ b/Documentation/admin-guide/kernel-parameters.txt
>> @@ -5901,7 +5901,7 @@
>> rodata= [KNL,EARLY]
>> on Mark read-only kernel memory as read-only (default).
>> off Leave read-only kernel memory writable for debugging.
>> - full Mark read-only kernel memory and aliases as read-only
>> + noalias Use more block mappings,may have better performance.
>> [arm64]
> Maybe use
> noalias Do not check aliases in order to allow larger kernel page
> sizes on a platforms without FEAT_BBM2 support[arm64])
>
> instead?
The "rodata=noalias" here is equal to original "rodata=on".
But Yang Shi's patch set works with original "rodata=full" :
https://lists.infradead.org/pipermail/linux-arm-kernel/2024-November/979770.html
IMHO, it's not proper to mention the FEAT_BBM in "rodata=noalias".
Thanks
Huang Shijie
Powered by blists - more mailing lists