From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754161Ab3JSAdS (ORCPT ); Fri, 18 Oct 2013 20:33:18 -0400 Received: from mail-pd0-f169.google.com ([209.85.192.169]:61843 "EHLO mail-pd0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752930Ab3JSAdQ (ORCPT ); Fri, 18 Oct 2013 20:33:16 -0400 In-Reply-To: References: <1382080184-19115-1-git-send-email-geert@linux-m68k.org> <172f2b40c29a29a470215c14250a559e@biophys.uni-duesseldorf.de> Mime-Version: 1.0 (Apple Message framework v624) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit Cc: linux-m68k , "linux-kernel@vger.kernel.org" From: Michael Schmitz Subject: Re: [PATCH] m68k/atari: Call paging_init() before nf_init() Date: Sat, 19 Oct 2013 13:33:07 +1300 To: Geert Uytterhoeven X-Mailer: Apple Mail (2.624) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Geert, > On Fri, Oct 18, 2013 at 9:29 AM, Michael Schmitz > wrote: >> does your fiddling with memory blocks in bootinfo now result in >> kernels >> being possible to boot in FastRAM? > > No, I only played with the start address of ST-RAM. > > Probably you can run a kernel in FastRAM with some minor tweaks if > you remove the ST-RAM block from the bootinfo, but then you loose > (at least) atafb :-) That, plus eventual ST-RAM bounce buffers for SCSI (which has been broken on my Falcon for a long time). > > With the DISCONTIGMEM memory model, the kernel must be stored in the > first memory block. As ST-RAM is before FastRAM in memory, you cannot > have the kernel in FastRAM without losing ST-RAM (as main memory --- > you can still e.g. ioremap() it for atafb, and use the rest of it as > swap through > a block device like z2ram. This is basically what we do on Amiga with > Chip RAM > and Z2 RAM). As long as we can ioremap() the ST-RAM frame buffer, we ought to be fine in the first instance. How useful ST-RAM as swap may be is debatable so I'd leave that aside for now. Main benefits would be for users of TTs that have been left out with recent kernel sizes. OK - how would I go about ioremaping a chunk of ST-RAM when that has been left out of the mm setup because it violates the discontigmem layout rules? Set up a kernel private mapping for all of ST-RAM, and make that available to the stram allocator? > With the SPARSEMEM memory model, you should be able to store the kernel > in FastRAM and have ST-RAM, too. I can still remember the headache I got when last playing with the mm code, I think I'll pass. Cheers, Michael > Gr{oetje,eeting}s, > > Geert > > -- > Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- > geert@linux-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