From: Andi Kleen <andi@firstfloor.org>
To: "Michael Chan" <mchan@broadcom.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH] bnx2: Fix IRQ failures during kdump.
Date: Sun, 30 May 2010 11:43:32 +0200 [thread overview]
Message-ID: <87ocfxzpvf.fsf@basil.nowhere.org> (raw)
In-Reply-To: <1275103462-8527-1-git-send-email-mchan@broadcom.com> (Michael Chan's message of "Fri\, 28 May 2010 20\:24\:22 -0700")
"Michael Chan" <mchan@broadcom.com> writes:
> When switching from the crashed kernel to the kdump kernel without going
> through PCI reset, IRQs may not work if a different IRQ mode is used on
PCIe with AER actually does support per link root port reset
(e.g. used for AER)
I've been wondering for some time if kexec should not simply
use that to reset all the devices, instead of addings hacks
around this to all drivers.
That would fix your problems too, right?
The question is just if AER is widely enough supported for this.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2010-05-30 9:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-29 3:24 [PATCH] bnx2: Fix IRQ failures during kdump Michael Chan
2010-05-29 5:33 ` David Miller
2010-05-29 6:45 ` Grant Grundler
2010-05-29 6:50 ` David Miller
2010-05-29 16:22 ` Michael Chan
2010-05-29 23:05 ` David Miller
2010-05-30 1:24 ` Matthew Wilcox
2010-05-30 3:49 ` David Miller
2010-05-30 9:44 ` Andi Kleen
2010-05-30 16:32 ` Michael Chan
2010-05-29 16:01 ` Stephen Hemminger
2010-05-30 9:43 ` Andi Kleen [this message]
2010-05-30 16:12 ` Michael Chan
2010-05-30 17:30 ` Andi Kleen
2010-05-31 4:43 ` Michael Chan
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=87ocfxzpvf.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=davem@davemloft.net \
--cc=linux-pci@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.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.