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: Mon, 14 May 2007 10:45:43 -0700	[thread overview]
Message-ID: <200705141045.44059.jesse.barnes@intel.com> (raw)
In-Reply-To: <20070421003020.A21503@jurassic.park.msu.ru>

On Friday, April 20, 2007 1:30 pm Ivan Kokshaysky wrote:
> On Fri, Apr 20, 2007 at 11:28:42AM -0700, Linus Torvalds wrote:
> > Actually, I would suggest we not do it automatically (because the
> > need for it is just so low, and the downsides are potentially huge
> > - there are just too many resources that are "hidden" from us
> > through ACPI tricks and having hardware that doesn't actually
> > expose their PCI resources fully through the normal PCI resource
> > setup).
>
> Definitely. I was intending to enable that *only* with some boot
> option.
>
> > Ivan, want to add some way to force that allocation (something like
> > "pci=assign-bus-resources")
>
> Yes, hopefully I'll get something in a next couple of days.

Any update on this, Ivan?  Maybe I missed your post, but I haven't seen 
anything yet...

Thanks,
Jesse

  reply	other threads:[~2007-05-14 17:46 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
2007-04-20 18:28           ` Linus Torvalds
2007-04-20 20:30             ` Ivan Kokshaysky
2007-05-14 17:45               ` Jesse Barnes [this message]
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=200705141045.44059.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.