From: Dave Hansen <haveblue@us.ibm.com>
To: "Martin J. Bligh" <mbligh@aracnet.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:23:52 -0700 [thread overview]
Message-ID: <1091046231.2871.379.camel@nighthawk> (raw)
In-Reply-To: <49810000.1091045752@flay>
On Wed, 2004-07-28 at 13:15, Martin J. Bligh wrote:
> However ... what happens to functions calling __pa that are called from
> boot time and run time code?
I've actually only run into one of those so far that I know of, and that
was on ppc64 (i386 had none that I found). In that one case, I used an
if(unlikely()) to optimize for the run-time one. There might be more,
but I think they're rare enough to just code it with an if() in each
case.
-- Dave
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <haveblue@us.ibm.com>
To: "Martin J. Bligh" <mbligh@aracnet.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:23:52 -0700 [thread overview]
Message-ID: <1091046231.2871.379.camel@nighthawk> (raw)
In-Reply-To: <49810000.1091045752@flay>
On Wed, 2004-07-28 at 13:15, Martin J. Bligh wrote:
> However ... what happens to functions calling __pa that are called from
> boot time and run time code?
I've actually only run into one of those so far that I know of, and that
was on ppc64 (i386 had none that I found). In that one case, I used an
if(unlikely()) to optimize for the run-time one. There might be more,
but I think they're rare enough to just code it with an if() in each
case.
-- Dave
--
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:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-27 22:00 Use of __pa() with CONFIG_NONLINEAR Dave Hansen
2004-07-27 22:00 ` Dave Hansen
2004-07-28 16:20 ` Joel Schopp
2004-07-28 16:20 ` Joel Schopp
2004-07-28 18:16 ` Mike Kravetz
2004-07-28 18:16 ` Mike Kravetz
2004-07-28 19:47 ` Martin J. Bligh
2004-07-28 19:47 ` Martin J. Bligh
2004-07-28 20:13 ` Dave Hansen
2004-07-28 20:13 ` Dave Hansen
2004-07-28 20:15 ` Martin J. Bligh
2004-07-28 20:15 ` Martin J. Bligh
2004-07-28 20:23 ` Dave Hansen [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=1091046231.2871.379.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=apw@shadowen.org \
--cc=jschopp@austin.ibm.com \
--cc=kravetz@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@aracnet.com \
/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.