From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Wilcox, Matthew R" <matthew.r.wilcox@intel.com>
Cc: Yinghai Lu <yinghai@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: linux-next: IO BAR sizing warning
Date: Wed, 6 May 2009 11:00:34 -0700 [thread overview]
Message-ID: <20090506110034.3c7d6e67@hobbes> (raw)
In-Reply-To: <CAC4B8726E86A142B27A9E9A2F2F1247AB7A8255@rrsmsx505.amr.corp.intel.com>
On Wed, 6 May 2009 11:41:12 -0600
"Wilcox, Matthew R" <matthew.r.wilcox@intel.com> wrote:
> I think PowerPC's IO_SPACE_LIMIT is defined incorrectly.
>
> On 64-bit, it's currently set to 0xffff'ffff'ffff'ffff. This can't
> possibly work, there's no way for the PCI bus to transmit 64-bit
> IO-port addresses. It should probably be defined to
>
> 0xffffffffU
TOP POSTER!
But yeah on a bus level it clearly needs to be limited to 32 bits, but
ISTR that some arches use the high resource bits for tracking I/O
resources on a systemwide basis (too lazy to look atm).
So either we need to split the definition between bus & resource usage,
or add a cast here...
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2009-05-06 18:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 4:30 linux-next: pci tree build warning Stephen Rothwell
2009-05-06 7:21 ` Yinghai Lu
2009-05-06 16:24 ` linux-next: IO BAR sizing warning Jesse Barnes
2009-05-06 17:41 ` Wilcox, Matthew R
2009-05-06 18:00 ` Jesse Barnes [this message]
2009-05-06 18:03 ` Wilcox, Matthew R
2009-06-03 6:49 ` Stephen Rothwell
2009-06-11 19:07 ` Jesse Barnes
2009-06-11 21:39 ` Benjamin Herrenschmidt
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=20090506110034.3c7d6e67@hobbes \
--to=jbarnes@virtuousgeek.org \
--cc=benh@kernel.crashing.org \
--cc=linux-next@vger.kernel.org \
--cc=matthew.r.wilcox@intel.com \
--cc=sfr@canb.auug.org.au \
--cc=yinghai@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 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).