public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: Alex Williamson <alex.williamson@hp.com>,
	jbarnes@virtuousgeek.org, yinghai@kernel.org,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] PCI: Always set prefetchable base/limit upper32 registers
Date: Mon, 30 Nov 2009 17:19:42 -0700	[thread overview]
Message-ID: <20091201001942.GF24539@lackof.org> (raw)
In-Reply-To: <20091201000332.GD24539@lackof.org>

On Mon, Nov 30, 2009 at 05:03:32PM -0700, Grant Grundler wrote:
> On Mon, Nov 30, 2009 at 02:51:44PM -0700, Alex Williamson wrote:
> > Prior to 1f82de10 we always initialized the upper 32bits of the
> > prefetchable memory window, regardless of the address range used.
> > Now we only touch it for a >32bit address, which means the upper32
> > registers remain whatever the BIOS initialized them too.
> > 
> > It's valid for the BIOS to set the upper32 base/limit to
> > 0xffffffff/0x00000000, which makes us program prefetchable ranges
> > like 0xffffffffabc00000 - 0x00000000abc00000
> > 
> > Revert the chunk of 1f82de10 that made this conditional so we always
> > write the upper32 registers and remove now unused pref_mem64 variable.
> > 
> > Signed-off-by: Alex Williamson <alex.williamson@hp.com>
> 
> Reviewed-by: Grant Grundler <grundler@parisc-linux.org>

NAK this - I messed up. Yinghai is correct. Something else is going on.

It might be perfectly OK to read 0xffffffffabc00000 if the bridge
isn't using the upper32 Prefetchable register. Maybe the problem is
some code is reading the upper32 value without checking that it's valid?

grant

  reply	other threads:[~2009-12-01  0:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-30 21:51 [PATCH v2] PCI: Always set prefetchable base/limit upper32 registers Alex Williamson
2009-12-01  0:03 ` Grant Grundler
2009-12-01  0:19   ` Grant Grundler [this message]
2009-12-01  1:23     ` Yinghai Lu
2009-12-01  4:10     ` Alex Williamson
2009-12-01 19:55       ` Grant Grundler
2009-12-01 20:40         ` Yinghai Lu
2009-12-01 20:59           ` Grant Grundler
2009-12-01 21:14             ` Yinghai Lu
2009-12-05  0:01 ` Jesse Barnes
2009-12-05 14:49   ` Alex Williamson

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=20091201001942.GF24539@lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=alex.williamson@hp.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --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