mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org,
	Andi Kleen <andi@firstfloor.org>,
	tglx@linutronix.de, hpa@zytor.com
Subject: Re: [PATCH 1/2] x86_64: fix mm.txt documentation
Date: Fri, 2 May 2008 09:22:26 +0200	[thread overview]
Message-ID: <20080502072226.GB713@elte.hu> (raw)
In-Reply-To: <1209635899-23018-1-git-send-email-jirislaby@gmail.com>


* Jiri Slaby <jirislaby@gmail.com> wrote:

> Commit 85eb69a16aab5a394ce043c2131319eae35e6493 introduced 512 MiB 
> sized kernel and 1.5 GiB sized module space but omitted to change 
> documentation properly. Fix that.

thanks Jiri, applied.

> [Wasn't the hole intentional protection hole?]

> -ffffffff80000000 - ffffffff82800000 (=40 MB)   kernel text mapping, from phys 0
> -... unused hole ...
> -ffffffff88000000 - fffffffffff00000 (=1919 MB) module mapping space
> +ffffffff80000000 - ffffffffa0000000 (=512 MB)  kernel text mapping, from phys 0
> +ffffffffa0000000 - fffffffffff00000 (=1536 MB) module mapping space

yep, the image was in a 128 MB chunk from which 88 MB was left empty and 
modules started at the next 128 MB boundary. The largest image i ever 
had was around 44MB, so i doubt it's an issue in practice. Mind doing a 
patch that reinstates it, by lowering the 512 image size limit to 508 
MB? [4MB should be more than enough in practice]

	Ingo

  parent reply	other threads:[~2008-05-02  7:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-01  9:58 Jiri Slaby
2008-05-01  9:58 ` [PATCH 2/2] x86_64: use PAGE_OFFSET in dump_pagetables Jiri Slaby
2008-05-02  7:33   ` Ingo Molnar
2008-05-02  7:22 ` Ingo Molnar [this message]
2008-05-02  7:57   ` [PATCH 1/2] x86_64: fix mm.txt documentation Jiri Slaby
2008-05-02  8:38   ` Andi Kleen
2008-05-02  8:47     ` Jiri Slaby
2008-05-02  8:00 ` Andi Kleen
2008-05-02  7:55   ` Jiri Slaby

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=20080502072226.GB713@elte.hu \
    --to=mingo@elte.hu \
    --cc=andi@firstfloor.org \
    --cc=hpa@zytor.com \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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
all inboxes | Powered by JetHome®