public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@in.ibm.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
	greg@kroah.com, Fastboot mailing list <fastboot@lists.osdl.org>,
	Morton Andrew Morton <akpm@osdl.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [RFC/PATCH] Kdump: Disabling PCI interrupts in capture kernel
Date: Sat,  4 Jun 2005 06:57:08 -0400	[thread overview]
Message-ID: <1117882628.42a1890479c23@imap.linux.ibm.com> (raw)

Quoting Alan Stern <stern@rowland.harvard.edu>:

> On Fri, 3 Jun 2005, Vivek Goyal wrote:
> 
> > In previous conversations, Alan Stern had raised the issue of console
> also
> > not working if interrupts are disabled on all the devices. I am not sure
> > but this should be working at least for serial consoles and vga text
> consoles.
> > May be sufficient to capture the dump.
> 
> This isn't an issue for x86.  It affects other architectures, in which the 
> system console is managed during the early stages of booting by the 
> platform firmware.  I suppose serial consoles would always work.
> 

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.

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.  

Thanks
Vivek

             reply	other threads:[~2005-06-04 10:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-04 10:57 Vivek Goyal [this message]
2005-06-04 15:35 ` [RFC/PATCH] Kdump: Disabling PCI interrupts in capture kernel Alan Stern
2005-06-04 18:26   ` Grant Grundler
  -- 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=1117882628.42a1890479c23@imap.linux.ibm.com \
    --to=vgoyal@in.ibm.com \
    --cc=akpm@osdl.org \
    --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