Date: Mon, 14 Jun 2010 09:18:23 +0900
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
       Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@redhat.com>,
       linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
       jbarnes@virtuousgeek.org
Subject: Re: [PATCH 2/4] x86: ioremap: fix physical address check
Message-Id: <20100614091823.34fac7a6.kamezawa.hiroyu@jp.fujitsu.com>
In-Reply-To: <4C1275BF.3070605@zytor.com>
References: <4C11FF10.4060203@jp.fujitsu.com>
	<4C11FFC0.1030006@jp.fujitsu.com>
	<4C1275BF.3070605@zytor.com>
Organization: FUJITSU Co. LTD.
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1005
Lines: 26

On Fri, 11 Jun 2010 10:43:27 -0700
"H. Peter Anvin" <hpa@zytor.com> wrote:

> On 06/11/2010 02:20 AM, Kenji Kaneshige wrote:
> > If the physical address is too high to be handled by ioremap() in
> > x86_32 PAE (e.g. more than 36-bit physical address), ioremap() must
> > return error (NULL). However, current x86 ioremap try to map this too
> > high physical address, and it causes unexpected behavior.
> 
> What unexpected behavior?  It is perfectly legitimately to map such a
> high address in PAE mode.  We have a 36-bit kernel-imposed limit on
> *RAM* in 32-bit mode (because we can't manage more than that), but there
> is no reason it should apply to I/O.
> 

I'm sorry for lack of study. 
How to access it via mapped area by ioremap() ?

Thanks,
-Kame

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/