All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Walle <bwalle@suse.de>
To: kexec@lists.infradead.org
Subject: Re: [makedumpfile] config file -- OSRELEASE
Date: Fri, 1 Jun 2007 15:48:57 +0200	[thread overview]
Message-ID: <20070601134857.GA9804@suse.de> (raw)
In-Reply-To: <m1myzj23ot.fsf@ebiederm.dsl.xmission.com>

* Eric W. Biederman <ebiederm@xmission.com> [2007-06-01 15:40]:
> Bernhard Walle <bwalle@suse.de> writes:
> 
> > * Ken'ichi Ohmichi <oomichi@mxs.nes.nec.co.jp> [2007-06-01 11:07]:
> >> 
> >> Now, the items makedumpfile cannot get from vmlinux statically are
> >> only version and page size. Do you have any idea for getting them
> >> from vmlinux ?
> >
> > I already tried to address a similar issue (version + command line
> > length for kexec-tools) by adding a ELF note. But it seems that kernel
> > hackers didn't like it.
> >
> > http://article.gmane.org/gmane.comp.boot-loaders.fastboot.general/3996/.
> 
> I'm not seeing the discussion there.

Because there was no real discussion about ELF notes here. I just
created this first patch as attempt to add ELF notes. The idea was
from Vivek Goyal.

> Looking at the patch I'm not quite certain of the composition of your
> notes. 

Well, it was a first attempt. I'm open to any suggestions about that
topic.


Thanks,
   Bernhard

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

      reply	other threads:[~2007-06-01 13:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29 19:30 [makedumpfile] config file -- OSRELEASE Bernhard Walle
2007-05-29 19:46 ` Jay Lan
2007-05-30 11:13 ` Ken'ichi Ohmichi
2007-05-31  8:57   ` Bernhard Walle
2007-05-31 19:14     ` Eric W. Biederman
2007-06-01  9:07       ` Ken'ichi Ohmichi
2007-06-01  9:52         ` Bernhard Walle
2007-06-01 13:40           ` Eric W. Biederman
2007-06-01 13:48             ` Bernhard Walle [this message]

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=20070601134857.GA9804@suse.de \
    --to=bwalle@suse.de \
    --cc=kexec@lists.infradead.org \
    /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.