From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: linux-pci@atrey.karlin.mff.cuni.cz
Cc: "Yinghai Lu" <yhlu.kernel@gmail.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Ingo Molnar" <mingo@elte.hu>,
"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-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: Tue, 29 Apr 2008 09:13:17 -0700 [thread overview]
Message-ID: <200804290913.17662.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <86802c440804251508w3607dc44yccc720899d94364b@mail.gmail.com>
On Friday, April 25, 2008 3:08 pm Yinghai Lu wrote:
> On Fri, Apr 25, 2008 at 2:48 PM, Jesse Barnes <jbarnes@virtuousgeek.org>
wrote:
> > On Wednesday, April 23, 2008 2:56 pm Yinghai Lu wrote:
> > > Yinghai found after using 2.6.25-rc3 later to kexec RHEL 5.1,
> > > NIC can not be used.
> > >
> > > bisected to
> >
> > Hi Yinghai, I've been thinking about these patches a bit... They seem
> > like an important bug fix (making sure kexec'd kernels work), but I'm a
> > bit worried that the kexec'd kernel can't handle potentially broken
> > MSI/INTx setups. Shouldn't the kexec'd kernel be a bit more robust? I
> > guess in this case you're kexec'ing an old kernel, so there's not much we
> > can do, but it still makes me a little uneasy.
>
> Yes, it is important, and should be in 2.6.25 stable too.
>
> the maskbits always 0x00 (enabled) from BIOS post..., so we should restore
> that.
>
> > I guess for this particular set it doesn't matter much, since we should
> > be restoring things in pci_msi*_shutdown and pci_shutdown_device either
> > way. Can you clean up the changelog a bit and maybe make it more concise?
> > E.g. we probably don't need the whole commit message for the bisect, and
> > we want to be clearer about what the failure mode is w/o the changes...
>
> without it, the second kernel can not use the devices, if second
> kernel could use MSI but doesn't touch mask_bit.
>
> ---
> [PATCH 1/2] pci/irq: restore mask_bits in msi shutdown -v3
>
> 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
>
> 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.
>
> So lets to restore the mask bit to it's pci reset defined value (enabled)
> when we disable the kernels use of msi.
>
> 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>
Applied both (fixed up the changelog a little though), thanks.
Jesse
prev parent reply other threads:[~2008-04-29 16:14 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 ` [PATCH 1/2] pci/irq: restore mask_bits in msi shutdown -v3 Yinghai Lu
2008-04-25 21:48 ` Jesse Barnes
2008-04-25 22:08 ` Yinghai Lu
2008-04-29 16:13 ` Jesse Barnes [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=200804290913.17662.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=greg@kroah.com \
--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 \
--cc=yhlu.kernel@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox