mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Yannick Roehlly <yannick.roehlly@free.fr>
Cc: Yinghai Lu <yinghai.lu@oracle.com>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -v2] pci: clear bridge resource size if BIOS assign bad one
Date: Fri, 11 Jun 2010 16:45:09 -0600	[thread overview]
Message-ID: <201006111645.10091.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <201006111044.42520.yannick.roehlly@free.fr>

On Friday, June 11, 2010 02:44:42 am Yannick Roehlly wrote:
> Le Thursday 10 June 2010 01:30:31 Bjorn Helgaas, vous avez écrit :
> > On Tuesday, June 08, 2010 05:36:33 pm Yinghai Lu wrote:
> > > On 06/08/2010 03:48 PM, Bjorn Helgaas wrote:
> > > > On Tuesday, June 08, 2010 03:43:50 pm Jesse Barnes wrote:
> > > > 
> > > > In this case, the aperture *size* from the BIOS is actually OK, but
> > > > the beginning of the aperture overlaps system memory.  With Yinghai's
> > > > patch, we reduce the size and move the start.  Windows was able to
> > > > just move the start of the aperture and preserve the original
> > > > 0x20000000 size (but I think it had to move something else out of
> > > > the way).
> > > 
> > > are you sure? that looks more aggressive.
> > 
> > I don't have the machine and can't be 100% sure, but based on what
> > Yannic reported here:
> > https://bugzilla.kernel.org/show_bug.cgi?id=16009#c11, it looks like
> > Windows moved that aperture.
> > 
> > I haven't used it myself, but possibly a program like SIV
> > (http://rh-software.com/) would give more detailed information
> > about what Windows is doing.
> 
> Hi Bjorn,
> 
> I don't know if it's useful, but here some output of SIV concerning PCI and 
> the Radeon card.

Can SIV generate a big dump of similar output for all devices at once?
Then I could avoid bugging you for "look at this, look at that," etc :-)

I'm particularly interested in the bridges (the PCIe root ports, in
this case).  I think Windows moved the 00:01.0 prefetchable aperture.
We know from the Linux dmesg that the 00:01.0 bridge was initially
configured like this:

  pci 0000:00:01.0: PCI bridge to [bus 01-01]
  pci 0000:00:01.0:   bridge window [io  0x7000-0x9fff]
  pci 0000:00:01.0:   bridge window [mem 0xfdd00000-0xfddfffff]
  pci 0000:00:01.0:   bridge window [mem 0xbdf00000-0xddefffff 64bit pref]

Based on https://bugzilla.kernel.org/show_bug.cgi?id=16009#c11, I think
Windows moved the prefetchable aperture:

  Plage mémoire: 00000000FDD00000 - 00000000FDDFFFFF
  Plage mémoire: 00000000C0000000 - 00000000DFFFFFFF   <== moved
  Plage d'E/S:   7000 - 9FFF

Note that the aperture size is still 0x20000000.

Since this new [mem 0xc0000000-0xdfffffff] aperture would conflict
with this 00:1c.4 aperture:

  pci 0000:00:1c.4:   bridge window [mem 0xddf00000-0xdfefffff 64bit pref]

I think it's likely that Windows moved the 1c.4 aperture as well (or
maybe even disabled it, since it leads to buses 06-07, and there are
no devices on those buses).

Bjorn

      reply	other threads:[~2010-06-11 22:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-16009-13546@https.bugzilla.kernel.org/>
     [not found] ` <201005191637.13177.bjorn.helgaas@hp.com>
     [not found]   ` <201005202236.20444.bjorn.helgaas@hp.com>
     [not found]     ` <201006021536.43333.bjorn.helgaas@hp.com>
     [not found]       ` <4C070ECA.2020309@oracle.com>
2010-06-03 20:43         ` Yinghai Lu
2010-06-03 23:02           ` Yannick Roehlly
2010-06-08 21:43           ` Jesse Barnes
2010-06-08 22:48             ` Bjorn Helgaas
2010-06-08 23:36               ` Yinghai Lu
2010-06-09 23:30                 ` Bjorn Helgaas
2010-06-11  8:44                   ` Yannick Roehlly
2010-06-11 22:45                     ` Bjorn Helgaas [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=201006111645.10091.bjorn.helgaas@hp.com \
    --to=bjorn.helgaas@hp.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=yannick.roehlly@free.fr \
    --cc=yinghai.lu@oracle.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

all inboxes | Powered by JetHome®