public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@in.ibm.com>
To: Maneesh Soni <maneesh@in.ibm.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
	Andrew Morton <akpm@osdl.org>,
	Neela.Kolli@engenio.com, linux-scsi@vger.kernel.org,
	mike.miller@hp.com, fastboot@lists.osdl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [Fastboot] [RFC] [PATCH 2/2] kdump: cciss driver initialization issue fix
Date: Mon, 26 Jun 2006 09:35:04 -0400	[thread overview]
Message-ID: <20060626133504.GA8985@in.ibm.com> (raw)
In-Reply-To: <20060626021100.GA12824@in.ibm.com>

On Mon, Jun 26, 2006 at 07:41:00AM +0530, Maneesh Soni wrote:
> On Sat, Jun 24, 2006 at 11:13:44AM -0600, Eric W. Biederman wrote:
> > Vivek Goyal <vgoyal@in.ibm.com> writes:
> > 
> > > On Sat, Jun 24, 2006 at 04:30:46AM -0700, Andrew Morton wrote:
> > >
> > >> > Or is there a generic way to handle these situations? Fixing them driver
> > >> > by driver is a long painful process. 
> > >> 
> > >> Some generic way of whacking a PCI device via the standard PCI registers? 
> > >> Not that I know of.
> > >
> > > Somebody hinted that think of PCI bus reset. But I think PCI bus reset will
> > > require firware/BIOS to export a hook to software to so initiate PCI bus
> > > reset and I don't think many platforms do that. Infact I am not even aware
> > > of one platform who does that.
> > 
> > Not all pci busses support it but there is a standard pci bus reset bit
> > in pci bridges.
> > 
> > I don't know if it would help but it might make sense to have a config
> > option that can be used to mark drivers that are known to have problems,
> > in these scenarios.
> > 
> > CONFIG_BRITTLE_INIT perhaps?
> > 
> > It would at least make it easier for people to see which drivers
> > they don't want to use, and give people some incentive to fix things.
> > 
> 
> Vivek, 
> 
> I think having something as Eric suggested instead of crashboot= is better.
> We can hve this config option set for kernel like dump capture
> kernel. (CONFIG_CRASH_DUMP=y). This should save some bytes on already longish
> kdump kernel boot paramenters.
> 

Maneesh, Keeping this code under a config option becomes a problem when we
will have a relocatable kernel. At some point of time we got to have
relocatable kernel so that people don't have to build two kernels. In fact
this is becoming a pain area for distros. That's the reason I thought
of making it a command line parameter.

I remember few months back, Eric had mentioned that he has got patches for
relocatable kernel ready for review for i386 and x86_64. Eric, do you have
any plans to post the patches for review?

Thanks
Vivek 

  reply	other threads:[~2006-06-26 13:35 UTC|newest]

Thread overview: 38+ 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 [this message]
2006-06-26 14:17                 ` Eric W. Biederman
2006-06-26 15:32                   ` 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                         ` 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                             ` Vivek Goyal
2006-06-26 17:52                             ` Eric W. Biederman
2006-06-26 18:18                               ` Vivek Goyal
2006-06-26 18:51                               ` Miller, Mike (OS Dev)
2006-06-26 19:21                                 ` Eric W. Biederman
2006-06-26 19:43                                   ` Vivek Goyal
2006-06-26 21:24                                   ` 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
2006-06-23 21:30 ` [RFC] [PATCH 1/2] introduce crashboot kernel command line parameter Bernd Eckenfels
2006-06-23 22:39   ` Vivek Goyal
2006-06-24  6:55 ` Andrew Morton

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=20060626133504.GA8985@in.ibm.com \
    --to=vgoyal@in.ibm.com \
    --cc=Neela.Kolli@engenio.com \
    --cc=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=maneesh@in.ibm.com \
    --cc=mike.miller@hp.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