public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Jesse Barnes <jesse.barnes@intel.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Robert Hancock <hancockr@shaw.ca>,
	linux-pci@atrey.karlin.mff.cuni.cz,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Possible issue with dangling PCI BARs
Date: Fri, 14 Dec 2007 10:09:28 +1100	[thread overview]
Message-ID: <1197587368.15741.187.camel@pasglop> (raw)
In-Reply-To: <20071214001239.B21652@jurassic.park.msu.ru>


On Fri, 2007-12-14 at 00:12 +0300, Ivan Kokshaysky wrote:
> On Fri, Dec 14, 2007 at 07:51:06AM +1100, Benjamin Herrenschmidt wrote:
> > If the device is behind a P2P bridge and the BIOS has set the windows of
> > that bridge so tightly that there is no room to allocate the MMIO BAR,
> > then a full disable/full enable would fail on a device that would
> > otherwise work using only PIO.
> 
> It won't be a problem with separate io/mmio enable.
> 
> > However, I'd be curious to see that happening in practice :-)
> > 
> > But I think it's fair enough to do an IO only / MEM only approach. I've
> > seen cases where IO is just not useable because of other constraints and
> > so I expect the MEM-only case to be more common, especially on non-x86.
> 
> Everybody wants MEM if it's available - it's just faster :-)
> So I guess a common case will be

 .../...

Right, I'm going to cook up some patch as time permit, maybe not before
next week tho.

Cheers,
Ben.



  reply	other threads:[~2007-12-13 23:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.YfTvVN5C3e6zwXPW5biWgeZ9XXc@ifi.uio.no>
     [not found] ` <fa.EhUqlM3V3y3HCcQkLBLSEKTJxBs@ifi.uio.no>
     [not found]   ` <fa.4FjaYKIciOijtgO+0DDrMkrLjv0@ifi.uio.no>
2007-12-13  4:22     ` Possible issue with dangling PCI BARs Robert Hancock
2007-12-13  5:26       ` Benjamin Herrenschmidt
2007-12-13  9:14         ` Ivan Kokshaysky
2007-12-13  9:29           ` Benjamin Herrenschmidt
2007-12-13  9:04       ` Ivan Kokshaysky
2007-12-13 10:24         ` Alan Cox
2007-12-13 11:17           ` Benjamin Herrenschmidt
2007-12-13 11:20             ` Benjamin Herrenschmidt
2007-12-13 20:04               ` Jesse Barnes
2007-12-13 20:51                 ` Benjamin Herrenschmidt
2007-12-13 21:12                   ` Ivan Kokshaysky
2007-12-13 23:09                     ` Benjamin Herrenschmidt [this message]
2007-12-13 21:02               ` Ivan Kokshaysky
2007-12-13 13:27             ` Alan Cox
2007-12-13  3:00 Benjamin Herrenschmidt
2007-12-13  3:04 ` Benjamin Herrenschmidt
2007-12-13  3:40   ` Benjamin Herrenschmidt
2007-12-14 11:52 ` Jon Masters
2007-12-14 22:11   ` Benjamin Herrenschmidt
2007-12-15  2:18     ` Jon Masters

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=1197587368.15741.187.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hancockr@shaw.ca \
    --cc=ink@jurassic.park.msu.ru \
    --cc=jesse.barnes@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox