From: Hugh Dickins <hugh@veritas.com>
To: carsteno@de.ibm.com
Cc: Andrew Morton <akpm@linux-foundation.org>,
Nick Piggin <npiggin@suse.de>,
Linux Memory Management List <linux-mm@kvack.org>,
mschwid2@linux.vnet.ibm.com, Holger Wolf <holger.wolf@de.ibm.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [patch] #ifdef very expensive debug check in page fault path
Date: Tue, 22 Jan 2008 22:35:17 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0801222226350.28823@blonde.site> (raw)
In-Reply-To: <479469A4.6090607@de.ibm.com>
On Mon, 21 Jan 2008, Carsten Otte wrote:
> Hugh Dickins wrote:
> >
> > Well: that patch still gets my Nack, but I guess I'm too late. If
> > s390 pagetables are better protected than x86 ones, add an s390 ifdef?
>
> The alternative would be to just make
> #define pfn_valid(pfn) (1)
> on s390. That would also get _us_ rid of the check while others do benefit. We
> would trap access to mem_map beyond its limits because we don't have a kernel
> mapping there. For us, it would not silently corrupt things but crash proper.
Whilst I quite like the sound of that, I wonder whether it's safe to
change s390's pfn_valid (rather surprisingly) for all its users. And
note that nobody but me has voiced any regret at the loss of the check.
My guess is we let it rest for now, and reconsider if a case comes up
later which would have got caught by the check (but the problem is that
such a case is much harder to identify than it was).
Hugh
--
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-01-22 22:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 18:01 Carsten Otte
2008-01-16 23:45 ` Nick Piggin
2008-01-17 0:10 ` Andrew Morton
2008-01-17 0:27 ` Nick Piggin
2008-01-18 20:56 ` Hugh Dickins
2008-01-21 9:45 ` Carsten Otte
2008-01-22 22:35 ` Hugh Dickins [this message]
2008-01-22 23:39 ` Nick Piggin
2008-01-23 0:02 ` Hugh Dickins
2008-01-23 9:14 ` Martin Schwidefsky
2008-01-17 9:53 ` Martin Schwidefsky
2008-01-18 4:09 ` 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=Pine.LNX.4.64.0801222226350.28823@blonde.site \
--to=hugh@veritas.com \
--cc=akpm@linux-foundation.org \
--cc=carsteno@de.ibm.com \
--cc=holger.wolf@de.ibm.com \
--cc=linux-mm@kvack.org \
--cc=mschwid2@linux.vnet.ibm.com \
--cc=npiggin@suse.de \
--cc=torvalds@linux-foundation.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