linux-kernel - Re: [PATCH 2/4] x86: ioremap: fix physical address check

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4C15E7F4.9090607@jp.fujitsu.com>
Date:	Mon, 14 Jun 2010 17:27:32 +0900
From:	Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>
To:	"H. Peter Anvin" <hpa@...or.com>
CC:	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
	linux-pci@...r.kernel.org, jbarnes@...tuousgeek.org
Subject: Re: [PATCH 2/4] x86: ioremap: fix physical address check

> Do you mean x86 linux can map physical address higher than 36-bit for I/O?
> My understanding is as follows.
> - Architectural limit of physical address in x86 32-bit mode is 40-bit
> (depnds on processor version).
> - The maximum physical address supported by current x86 linux kernel in
> 32-bit mode is 36-bit.
> On my environment, physical address higher than 40-bit (ex. 0xfc00001c000)
> is assigned to some PCI devices. I think there is no way to handle such
> high physical address in 32-bit mode.
>
> Thanks,
> Kenji Kaneshige

Please ignore above. I misunderstood the architectural limit of physical
address in x86 32-bit mode. It is not 40-bits, but 52-bits.

Thanks,
Kenji Kaneshige

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