From: Brian King <brking@us.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Greg KH <greg@kroah.com>, Paul Mackerras <paulus@samba.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] pci: Block config access during BIST
Date: Fri, 19 Nov 2004 17:22:54 -0600 [thread overview]
Message-ID: <419E804E.2050004@us.ibm.com> (raw)
In-Reply-To: <1100904402.3811.52.camel@gaston>
Benjamin Herrenschmidt wrote:
> On Fri, 2004-11-19 at 16:25 -0600, Brian King wrote:
>
>
>>I thought about that when writing up this patch, but decided against it.
>>I figured it was overkill and was going to make the patch more complicated
>>than it needed to be to solve the main problem I have seen, which is
>>userspace code, usually hotplug/coldplug scripts, reading config space
>>when an adapter is running BIST.
>
>
> How so ? Why would it be more complicated to do the workaround in
> drivers/pci/access.c macros instead and not touch all the wrappers ? It
> would actually make a much smaller patch...
I guess what I was having difficulty with was how to go from bus/devfn
to pci_dev in the bus macros (to access the saved_config_space) and do this
safely at interrupt level. The spinlock protecting the devices list on the
pci_bus struct is never acquired with irqsave and all the existing
functions to search for a given pci device are not callable from
interrupt context.
--
Brian King
eServer Storage I/O
IBM Linux Technology Center
next prev parent reply other threads:[~2004-11-19 23:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 20:23 [PATCH 1/2] pci: Block config access during BIST brking
2004-11-19 21:32 ` Greg KH
2004-11-19 22:25 ` Brian King
2004-11-19 22:46 ` Benjamin Herrenschmidt
2004-11-19 23:22 ` Brian King [this message]
2004-11-20 0:23 ` Benjamin Herrenschmidt
2004-11-19 22:45 ` Benjamin Herrenschmidt
2004-11-20 2:27 ` Alan Cox
2004-11-20 7:09 ` Benjamin Herrenschmidt
2004-11-20 12:42 ` Alan Cox
2004-11-20 22:32 ` Benjamin Herrenschmidt
2004-11-20 23:38 ` Brian King
2004-11-21 0:06 ` Benjamin Herrenschmidt
2004-11-21 1:55 ` Brian King
2004-11-21 7:03 ` Benjamin Herrenschmidt
2004-11-21 17:22 ` Brian King
2004-12-03 15:26 ` Brian King
2004-11-24 11:49 ` Alan Cox
2004-11-25 22:00 ` Paul Mackerras
2004-11-25 21:11 ` 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=419E804E.2050004@us.ibm.com \
--to=brking@us.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.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