public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@in.ibm.com>
To: Horms <horms@verge.net.au>
Cc: "Zou, Nanhai" <nanhai.zou@intel.com>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Fastboot mailing list <fastboot@lists.osdl.org>,
	Morton Andrew Morton <akpm@osdl.org>,
	Mohan Kumar M <mohan@in.ibm.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH] Kdump documentation update for 2.6.20
Date: Wed, 10 Jan 2007 10:13:16 +0530	[thread overview]
Message-ID: <20070110044316.GF8061@in.ibm.com> (raw)
In-Reply-To: <20070110015333.GC21005@verge.net.au>

On Wed, Jan 10, 2007 at 10:53:34AM +0900, Horms wrote:
> On Wed, Jan 10, 2007 at 09:34:12AM +0800, Zou, Nanhai wrote:
> > > >
> > > > I am hoping it --args-linux will be required while loading vmlinux on
> > > > IA64? Because this is ELF file specific option. And this interface should
> > > > be common across all the architectures.
> > > >
> > > > > Then again, I could be wrong, I'm not sure that I understand
> > > > > --args-linux, I just know that I'm not using it :)
> > >
> > > I will take a look into this.
> > >
> >  args-linux is not support by IA64 kdump.
> > To have common interface, maybe we should support it by ignore this
> > arg like ppc does.
> 
> That sounds reasonable to me. Vivek, what do you think?
> 

I think we should recognize --args-linux while loading elf image and
all the processing we do for loading linux elf vmlinux should be done
under that option (The way i386 does). This will help if down the line
kexec ia64 loader allows loading some other elf images where one needs
to prepare elf boot notes (--args-elf). 

Eric is the best person to comment on this. He has got all the background
about these options.

Thanks
Vivek

  reply	other threads:[~2007-01-10  4:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-08  7:58 [PATCH] Kdump documentation update for 2.6.20 Vivek Goyal
2007-01-09  1:18 ` Horms
2007-01-09 14:47   ` Vivek Goyal
2007-01-10  0:31     ` Horms
2007-01-10  1:34       ` Zou, Nanhai
2007-01-10  1:53         ` Horms
2007-01-10  4:43           ` Vivek Goyal [this message]
2007-01-10  5:37     ` Mohan Kumar M
2007-01-10  9:15       ` Vivek Goyal
2007-01-11  8:13         ` Horms

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=20070110044316.GF8061@in.ibm.com \
    --to=vgoyal@in.ibm.com \
    --cc=akpm@osdl.org \
    --cc=ebiederm@xmission.com \
    --cc=fastboot@lists.osdl.org \
    --cc=horms@verge.net.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mohan@in.ibm.com \
    --cc=nanhai.zou@intel.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