From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Ingo Molnar <mingo@redhat.com>,
tglx@linutronix.de, hpa@zytor.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Andi Kleen <andi@firstfloor.org>
Subject: Re: [PATCH 1/1] MM: virtual address debug
Date: Wed, 18 Jun 2008 22:51:02 +1000 [thread overview]
Message-ID: <200806182251.02486.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <1213271800-1556-1-git-send-email-jirislaby@gmail.com>
On Thursday 12 June 2008 21:56, Jiri Slaby wrote:
> Add some (configurable) expensive sanity checking to catch wrong address
> translations on x86.
>
> - create linux/mmdebug.h file to be able include this file in
> asm headers to not get unsolvable loops in header files
> - __phys_addr on x86_32 became a function in ioremap.c since
> PAGE_OFFSET, is_vmalloc_addr and VMALLOC_* non-constasts are undefined
> if declared in page_32.h
Uh, I have to disagree with this. __phys_addr is used in some really
performance critical parts of the kernel, and the function calls are
free mindset is just wrong. Even for modern x86 CPUs, the function
call return might take 10 cycles or more when you include all costs.
And for something like this
#define __phys_addr(x) ((x) - PAGE_OFFSET)
the code to call the function is probably bigger than inline generated
code anyway.
--
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-06-18 12:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 11:56 Jiri Slaby
2008-06-18 12:12 ` Ingo Molnar
2008-06-18 13:59 ` Ingo Molnar
2008-06-18 14:11 ` Jiri Slaby
2008-06-18 16:11 ` Jiri Slaby
2008-06-18 18:35 ` [PATCH v2] " Jiri Slaby
2008-06-19 11:34 ` Ingo Molnar
2008-06-18 12:51 ` Nick Piggin [this message]
2008-06-18 13:41 ` [PATCH 1/1] " Jiri Slaby
2008-06-18 14:01 ` Nick Piggin
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=200806182251.02486.nickpiggin@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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