From: Dave McCracken <dave.mccracken@oracle.com>
To: Andy Whitcroft <apw@shadowen.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: Page scan keeps touching kernel text pages
Date: Mon, 25 Feb 2008 13:46:32 -0600 [thread overview]
Message-ID: <200802251346.32289.dave.mccracken@oracle.com> (raw)
In-Reply-To: <20080225192127.GA20322@shadowen.org>
On Monday 25 February 2008, Andy Whitcroft wrote:
> I thought that init sections were deliberatly pushed to the end of the
> kernel when linked, cirtainly on my laptop here that seems to be so.
> That would make the first two "after" the kernel. The other two appear
> to be before the traditional kernel load address, which is 0x100000, so
> those pages are before not in the kernel?
I believe the memory below the kernel load address on x86 is returned to the
free memory pool at some point during boot, which would explain those
addresses.
Dave McCracken
WARNING: multiple messages have this Message-ID (diff)
From: Dave McCracken <dave.mccracken@oracle.com>
To: Andy Whitcroft <apw@shadowen.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: Page scan keeps touching kernel text pages
Date: Mon, 25 Feb 2008 13:46:32 -0600 [thread overview]
Message-ID: <200802251346.32289.dave.mccracken@oracle.com> (raw)
In-Reply-To: <20080225192127.GA20322@shadowen.org>
On Monday 25 February 2008, Andy Whitcroft wrote:
> I thought that init sections were deliberatly pushed to the end of the
> kernel when linked, cirtainly on my laptop here that seems to be so.
> That would make the first two "after" the kernel. The other two appear
> to be before the traditional kernel load address, which is 0x100000, so
> those pages are before not in the kernel?
I believe the memory below the kernel load address on x86 is returned to the
free memory pool at some point during boot, which would explain those
addresses.
Dave McCracken
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-02-25 19:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 14:47 Page scan keeps touching kernel text pages Jörn Engel
2008-02-24 14:47 ` Jörn Engel
2008-02-25 15:07 ` Andy Whitcroft
2008-02-25 15:07 ` Andy Whitcroft
2008-02-25 15:15 ` Jörn Engel
2008-02-25 15:15 ` Jörn Engel
2008-02-25 17:35 ` Jörn Engel
2008-02-25 17:35 ` Jörn Engel
2008-02-25 17:48 ` Dave Hansen
2008-02-25 17:48 ` Dave Hansen
2008-02-25 18:53 ` Jörn Engel
2008-02-25 18:53 ` Jörn Engel
2008-02-25 19:21 ` Andy Whitcroft
2008-02-25 19:21 ` Andy Whitcroft
2008-02-25 19:46 ` Dave McCracken [this message]
2008-02-25 19:46 ` Dave McCracken
2008-02-25 20:38 ` Jörn Engel
2008-02-25 20:38 ` Jörn Engel
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=200802251346.32289.dave.mccracken@oracle.com \
--to=dave.mccracken@oracle.com \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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.