From: Grant Grundler <grundler@parisc-linux.org>
To: Vivek Goyal <vgoyal@in.ibm.com>
Cc: greg@kroah.com,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
Fastboot mailing list <fastboot@lists.osdl.org>,
Morton Andrew Morton <akpm@osdl.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Bodo Eggert <7eggert@gmx.de>,
Dipankar Sarma <dipankar@in.ibm.com>,
Grant Grundler <grundler@parisc-linux.org>,
stern@rowland.harvard.edu, awilliam@fc.hp.com,
bjorn.helgaas@hp.com
Subject: Re: [RFC/PATCH] Kdump: Disabling PCI interrupts in capture kernel
Date: Mon, 6 Jun 2005 23:07:27 -0600 [thread overview]
Message-ID: <20050607050727.GB12781@colo.lackof.org> (raw)
In-Reply-To: <1118113637.42a50f65773eb@imap.linux.ibm.com>
On Mon, Jun 06, 2005 at 11:07:17PM -0400, Vivek Goyal wrote:
> So even if interrupts are disabled on PCI-PCI bridge, interrupts generated
> by PCI devices on secondary bus are not blocked and I hope device should
> be working fine.
How did you plan on disabling interrupts?
Did you see the MSI discussion that going on now in linux-pci mailing list?
> But at the same time kdump kernels are not supposed to
> do a great deal except capture and save the dump.
I'd think you want to stop DMA for all devices.
Just to prevent them from messing more with memory
that you want to dump - ie get a consistent snapshot.
Leaving VGA devices alone should be safe.
> Disabling interrupts at PCI level should increase the reliability of capturing
> the dump on newer machines with hardware compliant with PCI 2.3 or higher.
*lots* of PCI devices predate PCI2.3. Possibly even the majority.
hth,
grant
next prev parent reply other threads:[~2005-06-07 5:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 3:07 Vivek Goyal
2005-06-07 5:07 ` Grant Grundler [this message]
2005-06-07 9:59 ` Eric W. Biederman
2005-06-07 16:21 ` Grant Grundler
2005-06-07 18:42 ` [Fastboot] " Eric W. Biederman
2005-06-08 4:02 ` Grant Grundler
2005-06-08 4:38 ` Eric W. Biederman
2005-06-08 6:38 ` Vivek Goyal
2005-06-08 11:23 ` Vivek Goyal
-- strict thread matches above, loose matches on Subject: below --
2005-06-07 11:56 Vivek Goyal
[not found] <4bExX-3uT-11@gated-at.bofh.it>
2005-06-04 12:38 ` Bodo Eggert
2005-06-04 10:57 Vivek Goyal
2005-06-04 15:35 ` Alan Stern
2005-06-04 18:26 ` Grant Grundler
2005-06-04 10:43 Vivek Goyal
2005-06-03 11:25 Vivek Goyal
2005-06-03 11:54 ` Richard B. Johnson
2005-06-03 15:24 ` Alan Stern
2005-06-03 18:26 ` Eric W. Biederman
2005-06-03 18:21 ` Greg KH
2005-06-03 18:36 ` Eric W. Biederman
2005-06-04 13:18 ` Denis Vlasenko
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=20050607050727.GB12781@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=7eggert@gmx.de \
--cc=akpm@osdl.org \
--cc=awilliam@fc.hp.com \
--cc=bjorn.helgaas@hp.com \
--cc=dipankar@in.ibm.com \
--cc=ebiederm@xmission.com \
--cc=fastboot@lists.osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=vgoyal@in.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 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®