All of lore.kernel.org
 help / color / mirror / Atom feed
From: linas@austin.ibm.com (Linas Vepstas)
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Matthew Wilcox <matthew@wil.cx>,
	linux-scsi@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH]: PCI Error Recovery: Symbios SCSI device driver
Date: Tue, 31 Oct 2006 16:26:32 -0600	[thread overview]
Message-ID: <20061031222631.GQ6360@austin.ibm.com> (raw)
In-Reply-To: <1162322643.13859.54.camel@mulgrave.il.steeleye.com>

On Tue, Oct 31, 2006 at 02:24:01PM -0500, James Bottomley wrote:
> 
> Just for my own edification, what happens on the dual function (dual
> channel) boards?  We have two threads there and two separate I/O
> processors.  I assume a PCI error will kill both, 

Yes.

> do we need to do
> something about this?

I'm not sure, and actually, I have not thought about 
or tested this case for the symbios. 

The answer depends on the h/w design.  On PCI
multi-function cards, the PCI reset callbacks will 
get called for each PCI function. (Each function 
gets to vote/veto how it wants te reset to proceed).

If the hardware supports completely independent scsi 
host initialization for each scsi i/o processor, 
then things should just work. 

If some part of the card init sequence needs to run 
only once, even when there are two i/o processors, then
this needs to be protected against.  I presume that
using  if(0 == PCI_FUNC(pdev->devfn)) is enough to
make sure the hardware initilization is called only once 
for the card -- i.e. by calling it only for PCI
function zero. If there needs to be some additional 
locking to make sure that the card initialization
completes before the i/o processor initialization 
starts ... well, I don't know about that.

--linas




  reply	other threads:[~2006-10-31 22:26 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-20 18:05 [PATCH]: PCI Error Recovery: Symbios SCSI device driver Linas Vepstas
2006-10-31 18:55 ` Matthew Wilcox
2006-10-31 19:24   ` James Bottomley
2006-10-31 22:26     ` Linas Vepstas [this message]
2006-10-31 23:13   ` Linas Vepstas
2006-11-02  0:07     ` [PATCH v3]: " Linas Vepstas
2006-11-02  1:19       ` [PATCH v4]: " Linas Vepstas
2006-11-02  3:57         ` Matthew Wilcox
2006-11-02  4:46     ` [PATCH]: " Grant Grundler
2006-11-02  4:56       ` Matthew Wilcox
  -- strict thread matches above, loose matches on Subject: below --
2007-07-02 18:39 Linas Vepstas
2007-07-02 18:39 ` Linas Vepstas
2007-07-05 18:28 ` Andrew Morton
2007-07-05 18:28   ` Andrew Morton
2007-07-05 18:28   ` Andrew Morton
2007-07-05 18:54   ` Matthew Wilcox
2007-07-05 18:54     ` Matthew Wilcox
2007-08-02 22:53     ` Linas Vepstas
2007-08-02 22:53       ` Linas Vepstas
2006-09-21 23:13 Linas Vepstas
2006-09-21 23:13 ` Linas Vepstas
2006-09-22 22:06 ` Luca
2006-09-22 22:06   ` Luca
2006-09-22 23:32   ` Linas Vepstas
2006-09-22 23:32     ` Linas Vepstas
2006-09-22 23:39     ` Randy.Dunlap
2006-09-22 23:39       ` Randy.Dunlap
2006-09-22 23:39       ` Randy.Dunlap
2006-09-22 23:50       ` Linas Vepstas
2006-09-22 23:50         ` Linas Vepstas
2006-09-23  0:57         ` Randy.Dunlap
2006-09-23  0:57           ` Randy.Dunlap
2006-09-23  0:57           ` Randy.Dunlap
2006-02-02 20:15 [PATCH] " Linas Vepstas
2006-01-18 16:53 linas
2006-01-18 17:07 ` Matthew Wilcox
2006-01-18 17:54   ` linas

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=20061031222631.GQ6360@austin.ibm.com \
    --to=linas@austin.ibm.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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.