All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Seiji Aguchi <seiji.aguchi@hds.com>,
	"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Americo Wang <xiyou.wangcong@gmail.com>,
	Matthew Garrett <mjg@redhat.com>,
	"tony.luck@intel.com" <tony.luck@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jarod Wilson <jwilson@redhat.com>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"dle-develop@lists.sourceforge.net" 
	<dle-develop@lists.sourceforge.net>,
	Satoru Moriya <satoru.moriya@hds.com>
Subject: Re: [RFC][PATCH] Replace a function call chain of kmsg_dump(KMSG_DUMP_KEXEC) with static function calls
Date: Mon, 18 Jul 2011 07:43:34 -0400	[thread overview]
Message-ID: <20110718114334.GA31986@redhat.com> (raw)
In-Reply-To: <m14o2mjj5l.fsf@fess.ebiederm.org>

On Sat, Jul 16, 2011 at 09:16:06AM -0700, Eric W. Biederman wrote:

[..]
> Am I wrong in thinking that the core motivation behind this patch is
> that our EFI support sucks and thus kdump on EFI does not work on some
> platforms?

One of the arguments seems is that kdump might not work 100% of the
time and saving kernel messages atleast gets some information out
reliably.

I think being able to save dmesg to NVRAM, in general sounds good to
me (if done in a relatively clean manner). Especially if we can get
rid of code taking locks and code path executed after crash is not
tool long and relatively easy to audit.

Thanks
Vivek

WARNING: multiple messages have this Message-ID (diff)
From: Vivek Goyal <vgoyal@redhat.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "dle-develop@lists.sourceforge.net"
	<dle-develop@lists.sourceforge.net>,
	"tony.luck@intel.com" <tony.luck@intel.com>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Satoru Moriya <satoru.moriya@hds.com>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Jarod Wilson <jwilson@redhat.com>,
	Americo Wang <xiyou.wangcong@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Seiji Aguchi <seiji.aguchi@hds.com>,
	Matthew Garrett <mjg@redhat.com>
Subject: Re: [RFC][PATCH] Replace a function call chain of kmsg_dump(KMSG_DUMP_KEXEC) with static function calls
Date: Mon, 18 Jul 2011 07:43:34 -0400	[thread overview]
Message-ID: <20110718114334.GA31986@redhat.com> (raw)
In-Reply-To: <m14o2mjj5l.fsf@fess.ebiederm.org>

On Sat, Jul 16, 2011 at 09:16:06AM -0700, Eric W. Biederman wrote:

[..]
> Am I wrong in thinking that the core motivation behind this patch is
> that our EFI support sucks and thus kdump on EFI does not work on some
> platforms?

One of the arguments seems is that kdump might not work 100% of the
time and saving kernel messages atleast gets some information out
reliably.

I think being able to save dmesg to NVRAM, in general sounds good to
me (if done in a relatively clean manner). Especially if we can get
rid of code taking locks and code path executed after crash is not
tool long and relatively easy to audit.

Thanks
Vivek

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

  parent reply	other threads:[~2011-07-18 11:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-11 15:47 [RFC][PATCH] Replace a function call chain of kmsg_dump(KMSG_DUMP_KEXEC) with static function calls Seiji Aguchi
2011-07-11 15:47 ` Seiji Aguchi
2011-07-11 17:27 ` Matthew Garrett
2011-07-11 17:27   ` Matthew Garrett
2011-07-11 22:07 ` Vivek Goyal
2011-07-11 22:07   ` Vivek Goyal
2011-07-13  8:37 ` Américo Wang
2011-07-13  8:37   ` Américo Wang
2011-07-16 16:16 ` Eric W. Biederman
2011-07-16 16:16   ` Eric W. Biederman
2011-07-16 16:28   ` Matthew Garrett
2011-07-16 16:28     ` Matthew Garrett
2011-07-16 20:11     ` Eric W. Biederman
2011-07-16 20:11       ` Eric W. Biederman
2011-07-16 20:27       ` Matthew Garrett
2011-07-16 20:27         ` Matthew Garrett
2011-07-18 11:43   ` Vivek Goyal [this message]
2011-07-18 11:43     ` Vivek Goyal

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=20110718114334.GA31986@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=dle-develop@lists.sourceforge.net \
    --cc=ebiederm@xmission.com \
    --cc=hpa@zytor.com \
    --cc=jwilson@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg@redhat.com \
    --cc=satoru.moriya@hds.com \
    --cc=seiji.aguchi@hds.com \
    --cc=tony.luck@intel.com \
    --cc=xiyou.wangcong@gmail.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.