From: "Randy.Dunlap" <rddunlap@osdl.org>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Linus Torvalds <torvalds@osdl.org>, Dave <dave.jiang@gmail.com>,
linux-kernel@vger.kernel.org, smaurer@teja.com,
linux@arm.linux.org.uk, dsaxena@plexity.net,
drew.moseley@intel.com
Subject: Re: clean way to support >32bit addr on 32bit CPU
Date: Mon, 10 Jan 2005 19:38:57 -0800 [thread overview]
Message-ID: <41E34A51.3080005@osdl.org> (raw)
In-Reply-To: <20050111020550.GE2696@holomorphy.com>
William Lee Irwin III wrote:
> On Mon, Jan 10, 2005 at 05:30:25PM -0800, Linus Torvalds wrote:
>
>>I don't think ioaddr_t needs to match resources. None of the IO accessor
>>functions take "u64"s anyway - and aren't likely to do so in the future
>>either - so "unsigned long" should be good enough.
>>Having u64 for resource handling is mainly an issue for RAM and
>>memory-mapped IO (right now the 32-bit limit means that we throw away
>>information about stuff above the 4GB mark from the e820 interfaces on
>>x86, for example - that _happens_ to work because we never see anything
>>but RAM there anyway, but it means that /proc/iomem doesn't show all of
>>the system RAM, and it does mean that our resource management doesn't
>>actually handle 64-bit addresses correctly.
>>See drivers/pci/probe.c for the result:
>> "PCI: Unable to handle 64-bit address for device xxxx"
>>(and I do not actually think this has _ever_ happened in real life, which
>>makes me suspect that Windows doesn't handle them either - but it
>>inevitably will happen some day).
>
>
> I have a vague recollection of seeing a report of an ia32 device and/or
> machine with this property from John Fusco but am having a tough time
> searching the archives properly for it. I do recall it being around the
> time the remap_pfn_range() work was started, and I also claimed it as
> one of the motivators of it in one of my posts. I'm unaware of whether
> there are more general resources in John Fusco's situation.
>
> My follow-ups began with:
> Message-ID: <20040924021735.GL9106@holomorphy.com>
> References: <41535AAE.6090700@yahoo.com>
http://marc.theaimsgroup.com/?l=linux-mm&m=109598180125156&w=2
--
~Randy
next prev parent reply other threads:[~2005-01-11 3:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 23:34 clean way to support >32bit addr on 32bit CPU Dave
2005-01-11 0:01 ` Slade Maurer
2005-01-11 0:00 ` Deepak Saxena
2005-01-11 0:35 ` Slade Maurer
2005-01-11 0:04 ` Roland Dreier
2005-01-11 0:09 ` Linus Torvalds
2005-01-11 0:28 ` Randy.Dunlap
2005-01-11 1:30 ` Linus Torvalds
2005-01-11 2:05 ` William Lee Irwin III
2005-01-11 3:38 ` Randy.Dunlap [this message]
2005-01-11 17:39 ` Randy.Dunlap
2005-01-11 18:18 ` Linus Torvalds
2005-01-11 19:40 ` Dave
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=41E34A51.3080005@osdl.org \
--to=rddunlap@osdl.org \
--cc=dave.jiang@gmail.com \
--cc=drew.moseley@intel.com \
--cc=dsaxena@plexity.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=smaurer@teja.com \
--cc=torvalds@osdl.org \
--cc=wli@holomorphy.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;
as well as URLs for NNTP newsgroup(s).