From: Bernhard Walle <bwalle@suse.de>
To: Ken'ichi Ohmichi <oomichi@mxs.nes.nec.co.jp>
Cc: jlan@sgi.com, kexec@lists.infradead.org
Subject: Re: [makedumpfile] config file -- OSRELEASE
Date: Thu, 31 May 2007 10:57:57 +0200 [thread overview]
Message-ID: <20070531085757.GA2585@suse.de> (raw)
In-Reply-To: <20070530201328oomichi@mail.jp.nec.com>
Hello,
* Ken'ichi Ohmichi <oomichi@mxs.nes.nec.co.jp> [2007-05-30 13:13]:
> 2007/05/29 21:30:58 +0200, Bernhard Walle <bwalle@suse.de> wrote:
> >is there any reason why the kernel version saved in the configuration
> >file is the version of the running kernel and not the version for
> >which the config file is for?
>
> The reason is that makedumpfile gets a running kernel's page_size as
> a 1st-kernel's page_size. If they are different, makedumpfile cannot
> analyze /proc/vmcore and it fails. So I think a configuration file
> should be created while 1st-kernel is running.
I also didn't find a possibility to get the page size from a kernel
image without running the executable.
> >It's a big problem because my plan was to ship the configuration files
> >with the kernel RPMs in SLES. However, we don't build the kernels on
> >systems which run the kernel that is just built -- so that's not
> >possible.
>
> It is a good idea to ship the configuration files with the kernel RPMs.
> I think you can do it with current implementation, because you need
> only one configuration file for one kernel image.
>
> I think you can ship configuration files as follows:
>
> 1. Build a kernel file and a debuginfo file.
> 2. Boot the system with the above kernel file.
> 3. Generate a configration file from a debuginfo file.
> 4. Ship the configration file with the kernel RPM.
>
> Any problem to follow the method above ?
No, that's not possible because it would change our whole build
process. However, I just replace the OSRELEASE now after generating
the config file with the kernel that's built and change the page size
according to the .config on IA64. That works for now. I know it's not
the best solution, but the only practicable for now.
Thanks,
Bernhard
--
SUSE LINUX Products GmbH Tel. +49 (911) 74053-0
Maxfeldstr. 5 GF: Markus Rex
90409 Nürnberg, Germany HRB 16746 (AG Nürnberg)
OpenPGP DDAF6454: F61F 34CC 09CA FB82 C9F6 BA4B 8865 3696 DDAF 6454
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2007-05-31 8:58 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 [this message]
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
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=20070531085757.GA2585@suse.de \
--to=bwalle@suse.de \
--cc=jlan@sgi.com \
--cc=kexec@lists.infradead.org \
--cc=oomichi@mxs.nes.nec.co.jp \
/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.