public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jin Dongming <jin.dongming@np.css.fujitsu.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: LKLM <linux-kernel@vger.kernel.org>,
	Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
	Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Lon Hohberger <lhh@redhat.com>, Neil Horman <nhorman@redhat.com>
Subject: Re: [PATCH] [RFC][Patch x86-tip] add notifier before kdump
Date: Thu, 29 Oct 2009 16:52:05 +0900	[thread overview]
Message-ID: <4AE949A5.9080509@np.css.fujitsu.com> (raw)
In-Reply-To: <20091027150725.GD10513@redhat.com>

Hi Vivek

Vivek Goyal wrote:
> - Other thing, I think Eric Biederman suggested was that we need to see
>   the code that will be executed after crash so that it can be audited and
>   keep it in kernel instead of blindly exporting a hook to module and let
>   module do whatever it want to do.
> 

I am sorry for that I could not catch the meaning of above words. In my
understanding:
    If the code is already in current kernel and no matter whether it is built
    or modulized, the code could be added before crash_kexec. Is it right?

If my understanding is not right, please let me ask a question before we
provide the code.
    What kind of code is considered as nice code and could be added into
    current kernel? Could you give me some requirements or examples
    about nice code?
    
Best regards,
Jin Dongming

> So my question is, how about introducing some infrastructure in kdump
> initrd to send a notification out?
> 
> Thanks
> Vivek


  parent reply	other threads:[~2009-10-29  7:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-27  8:39 [PATCH] [RFC][Patch x86-tip] add notifier before kdump Jin Dongming
2009-10-27 15:07 ` Vivek Goyal
2009-10-27 16:16   ` Lon Hohberger
2009-10-29  4:12     ` Jin Dongming
2009-10-29  5:32       ` Eric W. Biederman
2009-10-29  7:48         ` Jin Dongming
2009-10-29  7:52   ` Jin Dongming [this message]
2009-10-29 18:43     ` Eric W. Biederman

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=4AE949A5.9080509@np.css.fujitsu.com \
    --to=jin.dongming@np.css.fujitsu.com \
    --cc=ebiederm@xmission.com \
    --cc=kaneshige.kenji@jp.fujitsu.com \
    --cc=lhh@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nhorman@redhat.com \
    --cc=seto.hidetoshi@jp.fujitsu.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox