All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jesse.barnes@intel.com>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Greg KH <gregkh@suse.de>, Adam Jackson <ajackson@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: PCI bridge range sizing bug
Date: Fri, 20 Apr 2007 09:32:51 -0700	[thread overview]
Message-ID: <200704200932.52181.jesse.barnes@intel.com> (raw)
In-Reply-To: <20070420132352.A19232@jurassic.park.msu.ru>

On Friday, April 20, 2007 2:23 am Ivan Kokshaysky wrote:
> On Thu, Apr 19, 2007 at 05:19:20PM -0700, Linus Torvalds wrote:
> > I think we used to *never* assign PCI bus resources on x86, but
> > that thing got fixed some time ago. Now I think we only re-assign
> > them if they were unassigned *or* if the assignment wasn't working
> > before. But I'm not 100% sure about that second part... It's been
> > working so well that I don't think we've had a lot of problems with
> > resource assignment lately, and I've paged it all out of my brain.
> >
> > Ivan, can you remind my tired old brain?
>
> No :-)  You are absolutely right - we re-assign only unassigned OR
> conflicting resources. And yes, x86 kernel does accept any enabled
> bridge ranges without looking at what is on the other side of the
> bridge.
>
> I think what we need is some very minimalistic validity check for
> BIOS bridge setup: calculate sums of resource ranges of each type
> (or just MEM and PREFETCH, should we care about IO these days?)
> for devices that are behind the bridge, even without taking alignment
> requirements into account. Then, if some window is too small, we just
> let the pci_assign_unassigned_resources to take care of that.

Sounds good, hopefully reassigning the bridge resources won't cause too 
much trouble.  Do you have time to hack this up?  If not, I could give 
it a try, as long as ajax is willing to test...

Thanks,
Jesse

  reply	other threads:[~2007-04-20 16:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1175812632.17147.12.camel@localhost.localdomain>
2007-04-19 23:11 ` PCI bridge range sizing bug Jesse Barnes
2007-04-19 23:40   ` Greg KH
2007-04-20  0:19     ` Linus Torvalds
2007-04-20  9:23       ` Ivan Kokshaysky
2007-04-20 16:32         ` Jesse Barnes [this message]
2007-04-20 18:28           ` Linus Torvalds
2007-04-20 20:30             ` Ivan Kokshaysky
2007-05-14 17:45               ` Jesse Barnes
2007-05-15 22:39                 ` Ivan Kokshaysky
2007-04-20 20:34             ` Jesse Barnes
2007-04-21  5:31               ` Rik van Riel

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=200704200932.52181.jesse.barnes@intel.com \
    --to=jesse.barnes@intel.com \
    --cc=ajackson@redhat.com \
    --cc=gregkh@suse.de \
    --cc=ink@jurassic.park.msu.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.