From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Ingo Molnar <mingo@elte.hu>
Cc: Soeren Sandmann Pedersen <sandmann@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: d451564 breakage
Date: Sat, 14 Nov 2009 08:19:19 +0000 [thread overview]
Message-ID: <20091114081919.GA29752@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20091114002138.GA9421@elte.hu>
On Sat, Nov 14, 2009 at 01:21:38AM +0100, Ingo Molnar wrote:
> What i was thinking of was a really simple thing in highmem.c (or
> rather, in include/linux/highmem.h, after kmap_types.h gets included):
>
> #ifndef KM_NMI
> # define KM_NMI -1
> #endif
> #ifndef KM_NMI_PTE
> # define KM_NMI_PTE -1
> #endif
>
> etc.
That means we need to ensure that kmap_atomic() fails when these are
used, to avoid kmap_atomic corrupting virtual mappings below the kmap
area should one of these be used. That means additional run-time code
in all those implementations - I'd much rather leave that to someone
else to do.
Alternatively, they could be wrapped with CONFIG_DEBUG_HIGHMEM so they
aren't normally visible.
In any case, as I've already pointed out, we still need to add definitions
to all places which define these constants. Having them exist as enum
constants does not make them visible to the preprocessor.
I don't think it's as simple as you're trying to make it. However,
since you seem to have a solid idea which you're trying to get me to
implement, maybe it'd just be much simpler and faster if you provided
that patch.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2009-11-14 8:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 15:11 d451564 breakage Russell King
2009-11-13 19:54 ` Andrew Morton
2009-11-13 22:50 ` Ingo Molnar
2009-11-13 22:48 ` Ingo Molnar
2009-11-13 23:02 ` Russell King
2009-11-13 23:17 ` Ingo Molnar
2009-11-13 23:37 ` Russell King
2009-11-14 0:21 ` Ingo Molnar
2009-11-14 8:19 ` Russell King [this message]
2009-11-14 9:28 ` Ingo Molnar
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=20091114081919.GA29752@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sandmann@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox