public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: vgoyal@in.ibm.com
Cc: linux-kernel@vger.kernel.org, fastboot@lists.osdl.org,
	linux-scsi@vger.kernel.org, ebiederm@xmission.com,
	mike.miller@hp.com
Subject: Re: [RFC] [PATCH 1/2] introduce crashboot kernel command line parameter
Date: Fri, 23 Jun 2006 23:55:14 -0700	[thread overview]
Message-ID: <20060623235514.48ea9578.akpm@osdl.org> (raw)
In-Reply-To: <20060623210121.GA18384@in.ibm.com>

On Fri, 23 Jun 2006 17:01:21 -0400
Vivek Goyal <vgoyal@in.ibm.com> wrote:

> o Add kernel command line option "crashboot"
> 
> o This option is an indication to the kernel that kernel is booting in an
>   unreliable environment where possibly BIOS execution has been skipped
>   and devices are left operational or in unknown state.
> 
> o Kernel, especially device drivers can use this option to take special
>   actions like soft-resetting the device, relaxing some of the rules
>   to make sure kernel can boot/device driver can initiliaze in this
>   environment.
> 
> o As of today this option is useful to Kdump. Kdump will pass this option
>   to second kernel to improve the reliability of successful kenrel boot/
>   device driver initializatoin. 

It worries me that this will be used to work around driver problems rather
than fixing them properly.


      parent reply	other threads:[~2006-06-24  6:55 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-23 21:01 [RFC] [PATCH 1/2] introduce crashboot kernel command line parameter Vivek Goyal
2006-06-23 21:04 ` [RFC] [PATCH 2/2] kdump: cciss driver initialization issue fix Vivek Goyal
2006-06-24  6:55   ` Andrew Morton
2006-06-24 11:19     ` Vivek Goyal
2006-06-24 11:30       ` Andrew Morton
2006-06-24 12:08         ` Vivek Goyal
2006-06-24 17:13           ` Eric W. Biederman
2006-06-26  2:11             ` [Fastboot] " Maneesh Soni
2006-06-26 13:35               ` Vivek Goyal
2006-06-26 14:17                 ` Eric W. Biederman
2006-06-26 15:32                   ` [Fastboot] " Vivek Goyal
2006-06-26 16:00                     ` Eric W. Biederman
2006-06-26 16:13                       ` Miller, Mike (OS Dev)
2006-06-26 16:35                         ` Vivek Goyal
2006-06-26 16:38                         ` [Fastboot] " Eric W. Biederman
2006-06-26 16:51                           ` Miller, Mike (OS Dev)
2006-06-26 17:04                             ` Vivek Goyal
2006-06-26 17:24                               ` Andrew Morton
2006-06-26 17:22                             ` [Fastboot] " Vivek Goyal
2006-06-26 17:52                             ` Eric W. Biederman
2006-06-26 18:18                               ` Vivek Goyal
2006-06-26 18:51                               ` [Fastboot] " Miller, Mike (OS Dev)
2006-06-26 19:21                                 ` Eric W. Biederman
2006-06-26 19:43                                   ` Vivek Goyal
2006-06-26 21:24                                   ` [Fastboot] " Miller, Mike (OS Dev)
2006-06-26 19:36                                 ` Vivek Goyal
2006-06-26 17:16                       ` Vivek Goyal
2006-06-26 17:31                         ` Andrew Morton
2006-06-26 17:39                         ` Eric W. Biederman
2006-06-26 17:56                           ` James Bottomley
2006-06-26 18:23                             ` Eric W. Biederman
2006-06-27  2:42                   ` [RFC] [PATCH 2/2] kdump: cciss driver initialization?issue fix Horms
2006-06-26  9:09             ` Horms
2006-06-26 13:45               ` [Fastboot] " Vivek Goyal
2006-06-27  2:30                 ` Horms
     [not found] ` <E1FttEj-0002JH-00@calista.eckenfels.net>
2006-06-23 22:39   ` [RFC] [PATCH 1/2] introduce crashboot kernel command line parameter Vivek Goyal
2006-06-24  6:55 ` Andrew Morton [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=20060623235514.48ea9578.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=ebiederm@xmission.com \
    --cc=fastboot@lists.osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mike.miller@hp.com \
    --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