From: Russell King <rmk@arm.linux.org.uk>
To: akpm@linux-foundation.org
Cc: andi@firstfloor.org, ak@linux.intel.com, ebiederm@xmission.com,
linux-arch@vger.kernel.org, rusty@rustcorp.com.au,
sam@ravnborg.org, mm-commits@vger.kernel.org
Subject: Re: [to-be-updated] add-a-kernel_address-that-works-for-data-too.patch removed from -mm tree
Date: Wed, 10 Mar 2010 20:43:47 +0000 [thread overview]
Message-ID: <20100310204346.GC24353@flint.arm.linux.org.uk> (raw)
In-Reply-To: <201003102029.o2AKTg4K001911@imap1.linux-foundation.org>
On Wed, Mar 10, 2010 at 12:29:42PM -0800, akpm@linux-foundation.org wrote:
>
> The patch titled
> add a kernel_address() that works for data too
> has been removed from the -mm tree. Its filename was
> add-a-kernel_address-that-works-for-data-too.patch
>
> This patch was dropped because an updated version will be merged
>
> The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
>
> ------------------------------------------------------
> Subject: add a kernel_address() that works for data too
> From: Andi Kleen <andi@firstfloor.org>
>
> Add a variant of kernel_text_address() that includes kernel data.
>
> Assumes kernel is _text ... _end - init section. True everywhere?
No, it is not. ARM XIP has text in one area, and the data in RAM.
There are two distinct sections:
_text .. _etext
_data .. _end
They both exclude the init sections on ARM, except when XIP is enabled
where the init data appears inside _data .. _end, and is demarked by
__init_begin .. __init_end.
Final point is that we end up with the Dwarf2 unwind tables after the
_etext, but not included in _data - I don't think that matters though.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
prev parent reply other threads:[~2010-03-10 20:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 20:29 [to-be-updated] add-a-kernel_address-that-works-for-data-too.patch removed from -mm tree akpm
2010-03-10 20:43 ` Russell King [this message]
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=20100310204346.GC24353@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=ebiederm@xmission.com \
--cc=linux-arch@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sam@ravnborg.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.