All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Bernhard Walle <bwalle@suse.de>,
	kexec@lists.infradead.org,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Remove CONFIG_EXPERIMENTAL from kdump
Date: Fri, 27 Jun 2008 17:13:09 +0900	[thread overview]
Message-ID: <20080627081309.GA11284@linux-sh.org> (raw)
In-Reply-To: <20080626123518.GA3878@redhat.com>

On Thu, Jun 26, 2008 at 08:35:18AM -0400, Vivek Goyal wrote:
> On Thu, Jun 26, 2008 at 10:28:03AM +0200, Bernhard Walle wrote:
> > * Andrew Morton [2008-06-26 01:23]:
> > > >  
> > > >  config PROC_VMCORE
> > > >          bool "/proc/vmcore support (EXPERIMENTAL)"
> > > > -        depends on PROC_FS && EXPERIMENTAL && CRASH_DUMP
> > > > +        depends on PROC_FS && CRASH_DUMP
> > > >  	default y
> > > >          help
> > > >          Exports the dump image of crashed kernel in ELF format.
> > > 
> > > What about powerpc, sh and ia64?
> > 
> > At least for ia64 I wouldn't consider it as experimental. Don't know
> > about SH and PPC. But should we mark it as EXPERIMENTAL on all
> > platforms only because some "exotic" (at least SH) platforms have kdump
> > not very long implemented?
> 
> It has been present long enough on ia64 and ppc64. Only new entry seems
> to be SH. I would think of leaving it EXPERIMENTAL only on SH.
> 
Yes, kdump should remain EXPERIMENTAL on SH for the time being. It's only
been tested on a tiny subset of CPUs, and will need additional work for
the rest (as with kexec for that matter).

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Bernhard Walle <bwalle@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Remove CONFIG_EXPERIMENTAL from kdump
Date: Fri, 27 Jun 2008 17:13:09 +0900	[thread overview]
Message-ID: <20080627081309.GA11284@linux-sh.org> (raw)
In-Reply-To: <20080626123518.GA3878@redhat.com>

On Thu, Jun 26, 2008 at 08:35:18AM -0400, Vivek Goyal wrote:
> On Thu, Jun 26, 2008 at 10:28:03AM +0200, Bernhard Walle wrote:
> > * Andrew Morton [2008-06-26 01:23]:
> > > >  
> > > >  config PROC_VMCORE
> > > >          bool "/proc/vmcore support (EXPERIMENTAL)"
> > > > -        depends on PROC_FS && EXPERIMENTAL && CRASH_DUMP
> > > > +        depends on PROC_FS && CRASH_DUMP
> > > >  	default y
> > > >          help
> > > >          Exports the dump image of crashed kernel in ELF format.
> > > 
> > > What about powerpc, sh and ia64?
> > 
> > At least for ia64 I wouldn't consider it as experimental. Don't know
> > about SH and PPC. But should we mark it as EXPERIMENTAL on all
> > platforms only because some "exotic" (at least SH) platforms have kdump
> > not very long implemented?
> 
> It has been present long enough on ia64 and ppc64. Only new entry seems
> to be SH. I would think of leaving it EXPERIMENTAL only on SH.
> 
Yes, kdump should remain EXPERIMENTAL on SH for the time being. It's only
been tested on a tiny subset of CPUs, and will need additional work for
the rest (as with kexec for that matter).

  parent reply	other threads:[~2008-06-27  8:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-25 21:49 [PATCH] Remove CONFIG_EXPERIMENTAL from kdump Bernhard Walle
2008-06-25 21:49 ` Bernhard Walle
2008-06-25 21:52 ` WANG Cong
2008-06-25 21:52   ` WANG Cong
2008-06-25 22:16 ` Vivek Goyal
2008-06-25 22:16   ` Vivek Goyal
2008-06-26  7:23   ` Bernhard Walle
2008-06-26  7:23     ` Bernhard Walle
2008-06-26  7:24     ` Bernhard Walle
2008-06-26  7:24       ` Bernhard Walle
2008-06-26  8:06     ` Ingo Molnar
2008-06-26  8:06       ` Ingo Molnar
2008-06-26  8:23     ` Andrew Morton
2008-06-26  8:23       ` Andrew Morton
2008-06-26  8:28       ` Bernhard Walle
2008-06-26  8:28         ` Bernhard Walle
2008-06-26  9:11         ` Bernhard Walle
2008-06-26  9:11           ` Bernhard Walle
2008-06-26 12:35         ` Vivek Goyal
2008-06-26 12:35           ` Vivek Goyal
2008-06-26 12:38           ` Bernhard Walle
2008-06-26 12:38             ` Bernhard Walle
2008-06-27  8:13           ` Paul Mundt [this message]
2008-06-27  8:13             ` Paul Mundt

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=20080627081309.GA11284@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=akpm@linux-foundation.org \
    --cc=bwalle@suse.de \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@redhat.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.