[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e1c594d7-d746-d0ce-2c55-fa3169f9bef1@nokia.com>
Date: Tue, 17 Nov 2020 10:41:44 +0100
From: Alexander Sverdlin <alexander.sverdlin@...ia.com>
To: Serge Semin <fancer.lancer@...il.com>
Cc: Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
Jiaxun Yang <jiaxun.yang@...goat.com>,
linux-mips@...r.kernel.org, Paul Burton <paulburton@...nel.org>,
linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH] MIPS: reserve the memblock right after the kernel
Hello Serge,
On 16/11/2020 23:31, Serge Semin wrote:
>> As completely unrelated optimization I can remove the same memblock_add() of the
>> kernel sections from the Octeon platform code.
> Why not as long as it will work. AFAICS the octeon platform code does
> some kernel start address adjustment while the generic MIPS code
> doesn't. Are you sure using the generic version for octeon won't cause
> any problem?
as I interpret this adjustment, this is open-coded virt_to_phys.
In my tests both code blocks reserve the same memory (well, generic code claims the rest of the last page,
and I'm going to fix this).
--
Best regards,
Alexander Sverdlin.
Powered by blists - more mailing lists