From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Mike Kravetz <kravetz@us.ibm.com>,
Andy Whitcroft <apw@shadowen.org>,
Joel Schopp <jschopp@austin.ibm.com>,
linux-mm <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Use of __pa() with CONFIG_NONLINEAR
Date: Wed, 28 Jul 2004 13:15:52 -0700 [thread overview]
Message-ID: <49810000.1091045752@flay> (raw)
In-Reply-To: <1091045615.2871.364.camel@nighthawk>
> On Wed, 2004-07-28 at 12:47, Martin J. Bligh wrote:
>> Can someone explain the necessity to create the new address space? We don't
>> need it with the current holes between nodes, and from my discssions with
>> Andy, I'm now unconvinced it's necessary.
>
> Actually, the new address space is quite separated from what I'm
> proposing here. I'd prefer to discuss that part when we have an
> implementation surrounding it. I can explain it now if you'd like, but
> it's going to be a bit harder with no code.
>
> The reason we need boot-time __{p,v}a() macros is really quite separate
> from the new (logical) address space. These new macros are just so we
> can assume flat addressing during boot or compile-time, before any
> nonlinear structures are set up.
Ah, OK ... makes more sense - thanks.
However ... what happens to functions calling __pa that are called from
boot time and run time code?
M.
--
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:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-07-28 20:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-27 22:00 Dave Hansen
2004-07-28 16:20 ` Joel Schopp
2004-07-28 18:16 ` Mike Kravetz
2004-07-28 19:47 ` Martin J. Bligh
2004-07-28 20:13 ` Dave Hansen
2004-07-28 20:15 ` Martin J. Bligh [this message]
2004-07-28 20:23 ` Dave Hansen
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=49810000.1091045752@flay \
--to=mbligh@aracnet.com \
--cc=apw@shadowen.org \
--cc=haveblue@us.ibm.com \
--cc=jschopp@austin.ibm.com \
--cc=kravetz@us.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox