All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linux-pci@atrey.karlin.mff.cuni.cz
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Possible issue with dangling PCI BARs
Date: Thu, 13 Dec 2007 14:04:58 +1100	[thread overview]
Message-ID: <1197515098.15741.64.camel@pasglop> (raw)
In-Reply-To: <1197514804.15741.60.camel@pasglop>


On Thu, 2007-12-13 at 14:00 +1100, Benjamin Herrenschmidt wrote:

 .../...

(oops, sent too fast)

> So not only we can have a dangling BAR, but nothing prevent us to
> actually go turn IO or MEM decoding on in case it wasn't already the
> case on that device.

And I was about to say before I clicked "send".. can't we do something like
writing all ff's into the BAR at the same time as we clear res->start ? Isn't
that supposed to pretty much disable decoding on that BAR ? Or not... Probably
still better than leaving it to whatever dangling value it had no ?

Also, maybe we should disable IO and MEM decoding by default on devices for
which one resource of that type failed to allocate ?

Ben.



  reply	other threads:[~2007-12-13  3:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-13  3:00 Possible issue with dangling PCI BARs Benjamin Herrenschmidt
2007-12-13  3:04 ` Benjamin Herrenschmidt [this message]
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
     [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     ` 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
2007-12-13 21:02               ` Ivan Kokshaysky
2007-12-13 13:27             ` Alan Cox

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=1197515098.15741.64.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --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 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.