All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Schmitz <schmitzmic@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org
Subject: Re: [PATCH] m68k: Increase initial mapping to 16MB if possible
Date: Fri, 25 Apr 2014 21:37:52 +1200	[thread overview]
Message-ID: <535A2CF0.7000301@gmail.com> (raw)
In-Reply-To: <87ppk7m3db.fsf@igel.home>

Thanks Andreas,
> If the size of the first memory chunk is at least 16MB increase the
> initial mapping to 16MB instead of 4MB.  This makes it possible to map
> more memory in the first node without running out of space for the page
> tables.
>
>   

Minor nit - the Falcon has 14MB, not 16MB. Not sure how large ST-RAM was 
on the TTs - trying for 8MB as well might be safer?

Cheers,

    Michael

> Signed-off-by: Andreas Schwab <schwab@linux-m68k.org>
> ---
>  arch/m68k/kernel/head.S | 9 ++++++++-
>  arch/m68k/mm/motorola.c | 2 +-
>  2 files changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/arch/m68k/kernel/head.S b/arch/m68k/kernel/head.S
> index ac85f16..23091ea 100644
> --- a/arch/m68k/kernel/head.S
> +++ b/arch/m68k/kernel/head.S
> @@ -941,7 +941,14 @@ L(nocon):
>   *	First map the first 4 MB of kernel code & data
>   */
>  
> -	mmu_map	#PAGE_OFFSET,%pc@(L(phys_kernel_start)),#4*1024*1024,\
> +	get_bi_record BI_MEMCHUNK
> +	movel	%a0@(4),%d0
> +	movel	#16*1024*1024,%d1
> +	cmpl	%d0,%d1
> +	jls	1f
> +	lsrl	#1,%d1
>   
+	cmpl	%d0,%d1
+	jls	1f
+	lsrl	#1,%d1

> +1:
> +	mmu_map	#PAGE_OFFSET,%pc@(L(phys_kernel_start)),%d1,\
>  		%pc@(m68k_supervisor_cachemode)
>  
>  	putc	'C'
> diff --git a/arch/m68k/mm/motorola.c b/arch/m68k/mm/motorola.c
> index 251c543..0e4c3a9 100644
> --- a/arch/m68k/mm/motorola.c
> +++ b/arch/m68k/mm/motorola.c
> @@ -45,7 +45,7 @@ EXPORT_SYMBOL(mm_cachebits);
>  #endif
>  
>  /* size of memory already mapped in head.S */
> -#define INIT_MAPPED_SIZE	(4UL<<20)
> +#define INIT_MAPPED_SIZE	(m68k_memory[0].size >= 16UL<<20 ? 16UL<<20 : 4UL<<20)
>  
>  extern unsigned long availmem;
>  
>   

  reply	other threads:[~2014-04-25  9:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24 10:24 [PATCH] m68k: Increase initial mapping to 16MB if possible Andreas Schwab
2014-04-25  9:37 ` Michael Schmitz [this message]
2014-04-29 10:11 ` Thorsten Glaser
2014-04-29 10:33   ` Andreas Schwab
2014-04-29 16:29     ` Geert Uytterhoeven
2014-04-29 16:43       ` Andreas Schwab
2014-04-30  7:38         ` Michael Schmitz
2014-05-25 16:57           ` Geert Uytterhoeven
2014-05-26  1:28             ` Michael Schmitz
2014-06-28 12:46             ` Andreas Schwab
2014-06-28 13:26               ` Geert Uytterhoeven
2014-06-28 13:49                 ` Andreas Schwab
2014-06-28 14:29                   ` Geert Uytterhoeven
2014-06-28 14:36                     ` Andreas Schwab
2014-06-28 15:55                       ` Geert Uytterhoeven
2014-06-28 16:27                         ` Andreas Schwab
2014-07-06  9:31                           ` Geert Uytterhoeven
2014-07-07 22:11                             ` Andreas Schwab
2014-07-08  7:23                               ` Geert Uytterhoeven

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=535A2CF0.7000301@gmail.com \
    --to=schmitzmic@gmail.com \
    --cc=linux-m68k@vger.kernel.org \
    --cc=schwab@linux-m68k.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.