linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jan Beulich <jbeulich@novell.com>
Cc: mingo@elte.hu, tglx@linutronix.de, hpa@zytor.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i386: reduce boot fixmap space
Date: Fri, 18 Jul 2008 07:48:13 -0700	[thread overview]
Message-ID: <4880AD2D.3050407@goop.org> (raw)
In-Reply-To: <4880A8AC.76E4.0078.0@novell.com>

Jan Beulich wrote:
> As 256 entries are needed, aligning to a 256-entry boundary is
> sufficient and still guarantees the single pte table requirement.
>   

I unified 32 and 64-bit early_ioremap by making 64-bit use the 32-bit 
early_ioremap.  In the process I put a similar entry in fixmap_64.h.  
Would you mind looking to see if the same change is relevant there?

Thanks,
    J

> Signed-off-by: Jan Beulich <jbeulich@novell.com>
>
> ---
>  include/asm-x86/fixmap_32.h |    6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> --- linux-2.6.26/include/asm-x86/fixmap_32.h	2008-07-13 23:51:29.000000000 +0200
> +++ 2.6.26-i386-btmap-fixmaps/include/asm-x86/fixmap_32.h	2008-07-18 13:51:16.000000000 +0200
> @@ -94,13 +94,13 @@ enum fixed_addresses {
>  	 * 256 temporary boot-time mappings, used by early_ioremap(),
>  	 * before ioremap() is functional.
>  	 *
> -	 * We round it up to the next 512 pages boundary so that we
> +	 * We round it up to the next 256 pages boundary so that we
>  	 * can have a single pgd entry and a single pte table:
>  	 */
>  #define NR_FIX_BTMAPS		64
>  #define FIX_BTMAPS_NESTING	4
> -	FIX_BTMAP_END = __end_of_permanent_fixed_addresses + 512 -
> -			(__end_of_permanent_fixed_addresses & 511),
> +	FIX_BTMAP_END = __end_of_permanent_fixed_addresses + 256 -
> +			(__end_of_permanent_fixed_addresses & 255),
>  	FIX_BTMAP_BEGIN = FIX_BTMAP_END + NR_FIX_BTMAPS*FIX_BTMAPS_NESTING - 1,
>  	FIX_WP_TEST,
>  #ifdef CONFIG_PROVIDE_OHCI1394_DMA_INIT
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>   


  reply	other threads:[~2008-07-18 14:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-18 12:29 [PATCH] i386: reduce boot fixmap space Jan Beulich
2008-07-18 14:48 ` Jeremy Fitzhardinge [this message]
2008-07-18 15:21   ` Jan Beulich
2008-07-18 23:18 ` H. Peter Anvin

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=4880AD2D.3050407@goop.org \
    --to=jeremy@goop.org \
    --cc=hpa@zytor.com \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).