From: Greg KH <greg@kroah.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: stable@kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org,
Peter Chubb <peterc@gelato.unsw.edu.au>,
jbarnes@virtuousgeek.org, matthew@wil.cx
Subject: Re: [stable] [patch] fix 64-vbit prefetchable memory resource BARs
Date: Mon, 3 Nov 2008 12:47:26 -0800 [thread overview]
Message-ID: <20081103204726.GB19936@kroah.com> (raw)
In-Reply-To: <200811031342.11018.bjorn.helgaas@hp.com>
On Mon, Nov 03, 2008 at 02:42:10PM -0600, Bjorn Helgaas wrote:
> On Sunday 12 October 2008 06:49:04 pm Peter Chubb wrote:
> > Since patch 6ac665c63dcac8fcec534a1d224ecbb8b867ad59
> > my infiniband controller hasn't worked. This is because it has
> > 64-bit prefetchable memory, which was mistakenly being taken to be
> > 32-bit memory. The resource flags in this case are
> > PCI_BASE_ADDRESS_MEM_TYPE_64|PCI_BASE_ADDRESS_MEM_PREFETCH.
> >
> > This patch checks only for the PCI_BASE_ADDRESS_MEM_TYPE_64 bit; thus
> > whether the region is prefetchable or not is ignored. This fixes my
> > Infiniband.
>
> I think this patch needs to be put in a 2.6.27-stable release.
>
> Without it, we ignore the upper bits of 64-bit prefetchable BARs.
>
> This is commit e354597cce8d219d135d65e585dc4f30323486b9 in Linus's
> tree.
Thanks for the info, we will queue it up.
greg k-h
prev parent reply other threads:[~2008-11-03 20:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 0:49 [patch] fix 64-vbit prefetchable memory resource BARs Peter Chubb
2008-10-13 1:34 ` Matthew Wilcox
2008-10-15 10:05 ` Jesse Barnes
2008-11-03 20:42 ` Bjorn Helgaas
2008-11-03 20:47 ` Greg KH [this message]
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=20081103204726.GB19936@kroah.com \
--to=greg@kroah.com \
--cc=bjorn.helgaas@hp.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=peterc@gelato.unsw.edu.au \
--cc=stable@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