Hi Geert, Mike,
I hadn't tested that series on actual hardware (just on ARAnyM), but as
it didn't appear to have any substantial changes from the previous one,
no objections from me.
Enabling out-of-order memory still gives me the nonzero mapcount errors,
though the additional memory does show up in the total memory count. I
need to test that on my 060 accelerator, whenever I get that to boot up
properly.
Cheers,
Michael
On 11/06/19 7:59 AM, Geert Uytterhoeven wrote:
Hi Mike,
On Mon, Jun 10, 2019 at 8:51 AM Mike Rapoport <rppt@xxxxxxxxxxxxx> wrote:
Gentle ping?
Sorry, due to a hardware issue, currently I cannot test kernels on my
Amiga (note that it does't have discontiguous memory chunks anyway,
poor 12 MiB FastRAM machine).
Anyone with an Amiga with 2 discontiguous chunks Fast RAM
(e.g. A3000/4000 with motherboard and accelerator RAM) who can give
this a try?
As Michael and Greg are already happy with this, I can apply it. We can
always sort out issues later.
Thanks for your patience!
On Thu, May 16, 2019 at 09:03:18AM +0300, Mike Rapoport wrote:
These pacthes replace DISCONTIGMEM with SPARSEMEM on m68k for systems with
!SINGLE_MEMORY_CHUNK set.
With SPARSEMEM there is a single node for the entire physical memory and to
cope with holes in the physical address space it is divided to sections of
up to 16M.
Each section has it's own memory map which size depends on actual populated
memory.
The section size of 16M was chosen pretty much arbitrarily as I couldn't
find specs for systems with e.g. Zorro memory extensions.
For the systems with ST-RAM and FastRAM, the switch to SPARSEMEM does not
change the limitation that if the kernel is loaded into the FastRam the
ST-RAM remains unmapped. It only ensures that if the kernel is loaded in
ST-RAM, the memory map is allocated from high physical addresses and then
atari/stram.c is able to reserve the frame buffer memory. If the kernel is
loaded to FastRAM, the ST-RAM remains unmapped as with DISCONTIGMEM and the
atari/stram.c maps it as IOMEM.
v2 changes:
* rebase on the current upstream
* make ColdFire MMU select SINGLE_MEMORY_CHUNK in Kconfig.cpu
Mike Rapoport (3):
m68k/mm: make node data and node setup depend on CONFIG_DISCONTIGMEM
m68k/mm: enable use of generic memory_model.h for !DISCONTIGMEM
m68k/mm: switch from DISCONTIGMEM to SPARSEMEM
arch/m68k/Kconfig.cpu | 14 ++++++--
arch/m68k/include/asm/page.h | 2 ++
arch/m68k/include/asm/page_mm.h | 6 +++-
arch/m68k/include/asm/sparsemem.h | 8 +++++
arch/m68k/include/asm/virtconvert.h | 2 +-
arch/m68k/mm/init.c | 8 ++---
arch/m68k/mm/motorola.c | 64 ++++++++++++++++++++++++++++++-------
7 files changed, 84 insertions(+), 20 deletions(-)
create mode 100644 arch/m68k/include/asm/sparsemem.h
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
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
