From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Andrew Morton" <akpm@linux-foundation.org>,
"Ingo Molnar" <mingo@elte.hu>
Cc: "Jesse Barnes" <jbarnes@virtuousgeek.org>,
"David Miller" <davem@davemloft.net>,
"Eric W. Biederman" <ebiederm@xmission.com>,
tglx@linutronix.de, "Greg KH" <greg@kroah.com>,
"Jeff Garzik" <jeff@garzik.org>,
linux-pci <linux-pci@atrey.karlin.mff.cuni.cz>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"James Bottomley" <James.Bottomley@hansenpartnership.com>,
"Sathya Prakash" <sathya.prakash@lsi.com>
Subject: Re: [PATCH 1/2] pci/irq: restore mask_bits in msi shutdown -v3
Date: Thu, 24 Apr 2008 17:40:22 -0700 [thread overview]
Message-ID: <86802c440804241740s53ae6587s909d307cf145d629@mail.gmail.com> (raw)
In-Reply-To: <200804231456.30786.yhlu.kernel@gmail.com>
On Wed, Apr 23, 2008 at 2:56 PM, Yinghai Lu <yhlu.kernel.send@gmail.com> wrote:
>
> Yinghai found after using 2.6.25-rc3 later to kexec RHEL 5.1,
> NIC can not be used.
>
> bisected to
>
> | commit 89d694b9dbe769ca1004e01db0ca43964806a611
> | Author: Thomas Gleixner <tglx@linutronix.de>
> | Date: Mon Feb 18 18:25:17 2008 +0100
> |
> | genirq: do not leave interupts enabled on free_irq
> |
> | The default_disable() function was changed in commit:
> |
> | 76d2160147f43f982dfe881404cfde9fd0a9da21
> | genirq: do not mask interrupts by default
> |
> | It removed the mask function in favour of the default delayed
> | interrupt disabling. Unfortunately this also broke the shutdown in
> | free_irq() when the last handler is removed from the interrupt for
> | those architectures which rely on the default implementations. Now we
> | can end up with a enabled interrupt line after the last handler was
> | removed, which can result in spurious interrupts.
> |
> | Fix this by adding a default_shutdown function, which is only
> | installed, when the irqchip implementation does provide neither a
> | shutdown nor a disable function.
> |
> | [@stable: affected versions: .21 - .24 ]
>
> for MSI, default_shutdown will call mask_bit for msi device. so all mask bits
> will left disabled after free_irq. then if kexec next kernel that only can
> use msi_enable bit. all device's MSI can not be used.
>
> want to try to restore MSI mask bits that is saved before using msi in first
> kernel.
>
> Eric said:
> This is over complicated and for hardware that erroneously triggers
> a msi irq after free_irq may have potential problems.
>
> So lets do the much simpler, much safer, and more general method of
> restoring the mask bit to it's pci reset defined value (enabled) when
> we disable the kernels use of msi.
>
> it will work, because pci_diable_msi is called after free_irq is called.
>
> v3: extend msi_set_mask_bit to msi_set_mask_bits to take mask, so we can fully
> restore that to 0x00 instead of 0xfe.
>
> Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com>
andrew,
this one should replace
[PATCH] x86_64: restore mask_bits in msi shutdown
in -mm
YH
next prev parent reply other threads:[~2008-04-25 0:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 4:48 [PATCH] pci: let pci_device_shutdown to call pci_disable_msi Yinghai Lu
2008-04-23 5:24 ` Michael Ellerman
2008-04-23 6:08 ` Yinghai Lu
2008-04-23 13:08 ` Eric W. Biederman
2008-04-23 17:31 ` Yinghai Lu
2008-04-24 0:17 ` Michael Ellerman
2008-04-24 1:22 ` Yinghai Lu
2008-04-24 2:11 ` Yinghai Lu
2008-04-23 12:57 ` Eric W. Biederman
2008-04-23 17:32 ` Yinghai Lu
2008-04-23 21:56 ` [PATCH 1/2] pci/irq: restore mask_bits in msi shutdown -v3 Yinghai Lu
2008-04-23 21:58 ` [PATCH 2/2] pci/irq: let pci_device_shutdown to call pci_msi_shutdown v2 Yinghai Lu
2008-04-25 0:40 ` Yinghai Lu [this message]
2008-04-25 21:48 ` [PATCH 1/2] pci/irq: restore mask_bits in msi shutdown -v3 Jesse Barnes
2008-04-25 22:08 ` Yinghai Lu
2008-04-29 16:13 ` Jesse Barnes
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=86802c440804241740s53ae6587s909d307cf145d629@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=greg@kroah.com \
--cc=jbarnes@virtuousgeek.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=mingo@elte.hu \
--cc=sathya.prakash@lsi.com \
--cc=tglx@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®