All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Vivek Goyal <vgoyal@in.ibm.com>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Greg KH <greg@kroah.com>,
	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>,
	awilliam@fc.hp.com, bjorn.helgaas@hp.com
Subject: Re: [RFC/PATCH] Kdump: Disabling PCI interrupts in capture kernel
Date: Sat, 4 Jun 2005 12:26:45 -0600	[thread overview]
Message-ID: <20050604182645.GD19823@colo.lackof.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0506041126030.5133-100000@iolanthe.rowland.org>

On Sat, Jun 04, 2005 at 11:35:59AM -0400, Alan Stern wrote:
> On Sat, 4 Jun 2005, Vivek Goyal wrote:
> 
> > Hi Alan, I know very little about consoles and their working.
> > I had a question. Even if console is being managed by platform firmware, in
> > initial states of booting, does it require interrupts to be enabled at 
> > VGA contorller (at least for the simple text mode). I was quickly browsing
> > through drivers/video/console/vgacon.c and did not look like that this
> > console driver needed interrupts to be enabled at the controller.
> 
> This isn't an issue for VGA, as far as I know.  It applies to
> architectures like PPC-64 and perhaps Alpha or PA-Risc.  And I don't know
> the details; ask Grant Grundler.

I'm more familiar with the serial consoles and how PDC interacts with them.
>From HP, both Alex Williamson and Bjorn Helgaas know more about
VGA support. I've cc'd both.

> > Anyway, looks like serial consoles will always work. So at least this can be
> > done for kdump case (CONFIG_CRASH_DUMP) and not generic kernel. Or, as I
> > mentioned in previous mail, while pre-loading capture kernel, pass a command
> > line parameter containing pci dev id of console and capture kernel does not 
> > disable interrupts on this console.  

parisc serial consoles don't need interrupts enabled. The serial device
does need it's MMIO and/or IO Port range enabled (I forgot which).
ISTR most serial consoles don't do DMA and thus don't need BusMaster
enabled in the PCI command register either.

> I suspect you're right that implementing this only in kdump kernels will 
> work okay.
> 
> For people interesting in reading some old threads on the subject, here 
> are some pointers:
> 
> http://marc.theaimsgroup.com/?l=linux-usb-devel&m=111055702309788&w=2
> 
> http://marc.theaimsgroup.com/?l=linux-kernel&m=98383052711171&w=2

wow...from 2001.
That's when we first release a500 support with Debian 3.0.

thanks,
grant

  reply	other threads:[~2005-06-04 18:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-04 10:57 [RFC/PATCH] Kdump: Disabling PCI interrupts in capture kernel Vivek Goyal
2005-06-04 15:35 ` Alan Stern
2005-06-04 18:26   ` Grant Grundler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-06-07 11:56 Vivek Goyal
2005-06-07  3:07 Vivek Goyal
2005-06-07  5:07 ` Grant Grundler
2005-06-07  9:59   ` Eric W. Biederman
2005-06-07 16:21     ` Grant Grundler
     [not found] <4bExX-3uT-11@gated-at.bofh.it>
2005-06-04 12:38 ` Bodo Eggert
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=20050604182645.GD19823@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 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.