From: linas@austin.ibm.com (Linas Vepstas)
To: Ananda Raju <Ananda.Raju@neterion.com>
Cc: Wen Xiong <wenxiong@us.ibm.com>,
linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
netdev@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] s2io: add PCI error recovery support
Date: Wed, 25 Oct 2006 10:11:24 -0500 [thread overview]
Message-ID: <20061025151123.GF6360@austin.ibm.com> (raw)
In-Reply-To: <78C9135A3D2ECE4B8162EBDCE82CAD77DC1C9B@nekter>
On Wed, Oct 25, 2006 at 02:29:33AM -0400, Ananda Raju wrote:
> Hi,
>
> s2io_card_down() will do few BAR0 read/write. As per
> pci-error-recovery.txt Documentation we are not supposed to do any new
> IO in error_detected().
Hmm, actually, its harmless to do further i/o. The s2io driver barks
(as it should) because the result of reads is always 0xffffffff.
> Can you try using
>
> atomic_set(&sp->card_state, CARD_DOWN);
>
> instead of s2io_card_down().
I will try that. I was mostly concerned that s2io_card_down()
also may do some other "important" things with regards to the driver
state, things which might be needed to keep the down-up sequence
symmetrical. I wasn't sure, so I took the conservative route.
> Also we have to add following if statement in beginning of s2io_isr().
>
> if (atomic_read(&nic->card_state) == CARD_DOWN)
> return IRQ_NOTHANDLED.
Right! Will revise this patch shortly.
> If it is ok to do BAR0 read/write in error_detected() then patch is OK.
Its OK on pSeries, and I beleive it will be OK on PCIE, but I do
not quite know enough about actual PCIE chipsets.
--linas
next prev parent reply other threads:[~2006-10-25 15:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 6:29 [PATCH] s2io: add PCI error recovery support Ananda Raju
2006-10-25 15:11 ` Linas Vepstas [this message]
2006-10-25 20:55 ` Linas Vepstas
-- strict thread matches above, loose matches on Subject: below --
2007-03-07 0:42 Ramkrishna Vepa
2007-03-05 22:33 Ramkrishna Vepa
2007-03-16 19:49 ` Linas Vepstas
2007-03-16 19:58 ` Ramkrishna Vepa
2007-02-15 23:08 Linas Vepstas
2007-01-10 19:54 Ramkrishna Vepa
2006-10-27 11:35 Ananda Raju
2006-10-27 19:32 ` Linas Vepstas
2006-10-26 9:56 Ananda Raju
2006-10-26 22:51 ` Linas Vepstas
2006-10-24 21:54 Linas Vepstas
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=20061025151123.GF6360@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=Ananda.Raju@neterion.com \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=netdev@vger.kernel.org \
--cc=wenxiong@us.ibm.com \
/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.