From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Brandon Philips <bphilips@suse.de>
Cc: Ramkrishna Vepa <Ramkrishna.Vepa@neterion.com>,
netdev@vger.kernel.org, teheo@suse.de,
e1000-devel@lists.sourceforge.net
Subject: Re: [patch 1/5][RFC] NET: Change pci_enable_device topci_reenable_device to keep device enable balance
Date: Thu, 09 Aug 2007 13:49:20 -0700 [thread overview]
Message-ID: <46BB7DD0.1000509@intel.com> (raw)
In-Reply-To: <20070809204552.GA6870@ifup.org>
Brandon Philips wrote:
> On 17:30 Wed 08 Aug 2007, Ramkrishna Vepa wrote:
>> Before slot_reset event is called io_error_detected could be called
>> (where pci_disable_device() is called), right?
>
> Oops! Right, the documentation says .error_detected is _always_ called
> before .slot_reset. So, this patch is not correct. Please don't merge
> this.
>
> From Documentation/pci-error-recovery.txt:
>
> STEP 1: Notification
> --------------------
> Platform calls the error_detected() callback on every instance of
> every driver affected by the error.
> ...
>
> If any driver requested a slot reset (by returning PCI_ERS_RESULT_NEED_RESET),
> then recovery proceeds to STEP 4 (Slot Reset).
>
>> The pci_reenable_device() will call enable only if the device was
>> enabled before and would not be enabled if the device were disabled. Is
>> this the intended behavior?
>
> Yes, you are right. And no it isn't.
it would be great if you can convince Linas Vepstas to review and ack your patch
- he's the one who knows the error handling code the best.
Auke
prev parent reply other threads:[~2007-08-09 20:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 22:44 [patch 1/5][RFC] NET: Change pci_enable_device to pci_reenable_device to keep device enable balance Brandon Philips
2007-08-03 9:00 ` Tejun Heo
2007-08-08 21:30 ` [patch 1/5][RFC] NET: Change pci_enable_device topci_reenable_device " Ramkrishna Vepa
2007-08-09 20:45 ` Brandon Philips
2007-08-09 20:49 ` Kok, Auke [this message]
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=46BB7DD0.1000509@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=Ramkrishna.Vepa@neterion.com \
--cc=bphilips@suse.de \
--cc=e1000-devel@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=teheo@suse.de \
/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.