From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] export e820 table on x86
Date: 21 Nov 2002 16:53:04 -0800 [thread overview]
Message-ID: <arjv5g$c2b$1@cesium.transmeta.com> (raw)
In-Reply-To: Pine.LNX.4.44.0211211556340.5779-100000@penguin.transmeta.com
Followup to: <Pine.LNX.4.44.0211211556340.5779-100000@penguin.transmeta.com>
By author: Linus Torvalds <torvalds@transmeta.com>
In newsgroup: linux.dev.kernel
>
> See also how we artificially only show 32-bit resources, because "struct
> resource" uses "unsigned long". That's a design mistake, and it _should_
> be "u64" (this actually could cause problems already on 64-bit PCI on
> 32-bit hosts, although it appears that nobody even tries to map devices
> past the 4GB area anyway), but I've never had a test-case for fixing it
> and seeing any difference.
>
Perhaps an abstract type, like resaddr_t, would make more sense? That
way we'll have less of an issue when the next category of weird system
architecture comes along, which may want some kind of node-based
addressing, who knows...
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-11-22 0:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 2:00 [PATCH] export e820 table on x86 Dave Hansen
2002-11-21 2:09 ` Christoph Hellwig
2002-11-21 21:01 ` Dave Hansen
2002-11-21 22:50 ` Linus Torvalds
2002-11-21 23:46 ` Dave Hansen
2002-11-22 0:04 ` Linus Torvalds
2002-11-22 0:53 ` H. Peter Anvin [this message]
2002-11-22 6:20 ` Eric W. Biederman
2002-11-22 7:50 ` Dave Hansen
2002-11-22 8:00 ` Linus Torvalds
2002-11-22 17:17 ` Eric W. Biederman
2002-11-22 22:37 ` Dave Hansen
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='arjv5g$c2b$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.