From: Grant Grundler <grundler@parisc-linux.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Grant Grundler <grundler@parisc-linux.org>,
Morton Andrew Morton <akpm@osdl.org>,
awilliam@fc.hp.com, greg@kroah.com,
Fastboot mailing list <fastboot@lists.osdl.org>,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
Bodo Eggert <7eggert@gmx.de>,
stern@rowland.harvard.edu, bjorn.helgaas@hp.com
Subject: Re: [Fastboot] Re: [RFC/PATCH] Kdump: Disabling PCI interrupts in capture kernel
Date: Tue, 7 Jun 2005 22:02:53 -0600 [thread overview]
Message-ID: <20050608040253.GA21060@colo.lackof.org> (raw)
In-Reply-To: <m1acm2vwil.fsf@ebiederm.dsl.xmission.com>
On Tue, Jun 07, 2005 at 12:42:42PM -0600, Eric W. Biederman wrote:
> The howto deal with an IOMMU has been sorted out but so far no one
> has actually done it. What has been discussed previously is simply
> reserving a handful of IOMMU entries,
How? with dma_alloc_consistent() or some special hook?
I'm just curious.
...
> and then only using those
> in the crash recover kernel. This is essentially what we do with DMA
> on architectures that don't have an IOMMU and it seems quite safe
> enough there.
Yeah, in general that should be feasible.
One might be able to trivially allocate a small, seperate IO PDIR
just for KDUMP and switch to that. Key thing is it be physically
contiguous in memory. Very little code is involved with IO Pdir
setup for both parisc and IA64. I can't speak for Alpha/sparc/ppc/et al.
...
> Well we are at least capable of multitasking but that is no longer the
> primary focus. Having polling as at least an option should make
> debugging easier. Last I looked Andrews kernel hand an irqpoll option
> to do something very like this.
You could run the itimer but I don't see why you should.
Kdump is essentially an embedded linux kernel. It really
doesn't need to be premptive multitasking either.
Anyway, sounds like you guys are on the right track.
thanks,
grant
next prev parent reply other threads:[~2005-06-08 3:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 3:07 [RFC/PATCH] Kdump: Disabling PCI interrupts in capture kernel Vivek Goyal
2005-06-07 5:07 ` Grant Grundler
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 [this message]
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-04 10:31 Maneesh Soni
2005-06-03 11:25 Vivek Goyal
2005-06-03 18:21 ` Greg KH
2005-06-03 18:36 ` Eric W. Biederman
2005-06-04 13:18 ` Denis Vlasenko
2005-06-04 13:43 ` [Fastboot] " Dipankar Sarma
2005-06-04 14:03 ` Dipankar Sarma
2005-06-04 21:14 ` Eric W. Biederman
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=20050608040253.GA21060@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=ebiederm@xmission.com \
--cc=fastboot@lists.osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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