public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Vivek Goyal <vgoyal@in.ibm.com>
Cc: Fernando Luis Vazquez Cao <fernando@intellilink.co.jp>,
	fastboot <fastboot@lists.osdl.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: Query: Kdump: Core Image ELF Format
Date: 23 Mar 2005 12:54:05 -0700	[thread overview]
Message-ID: <m18y4ervdu.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <1111574173.4756.20.camel@localhost.localdomain>

Vivek Goyal <vgoyal@in.ibm.com> writes:

> On Wed, 2005-03-23 at 13:26 +0900, Fernando Luis Vazquez Cao wrote:
> > Hi all.
> > 
> > On Tue, 2005-03-08 at 18:20 +0530, vivek goyal wrote:
> > > Core image ELF headers are prepared before crash and stored at a safe
> > > place in memory. These headers are retrieved over a kexec boot and final
> > > elf core image is prepared for analysis. 
> > 
> > Regarding the preparation of the ELF headers, I think we should also
> > take into consideration hot-plug memory and create appropriate
> > mechanisms to deal with it.
> > 
> > Assuming that both insertion and removal of memory trigger a hotplug
> > event that is subsequently handled by the relevant hotplug agent(*), the
> > latter could be modified so that, on successful memory onlining,
> > additional PT_LOAD headers are created and tucked in a safe place
> > together with the others.
> 
> I think, re-loading the panic kernel in such event should be an easier
> solution. Current kexec system call interface does not allow to read
> back already stored segments, which is necessary to append new PT_LOAD
> headers to the existing program header list and update ELF header.

I thought that is what he was describing.

Eric

  reply	other threads:[~2005-03-23 19:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-08 12:50 Query: Kdump: Core Image ELF Format vivek goyal
2005-03-08 15:14 ` Dave Anderson
2005-03-08 18:11   ` Eric W. Biederman
2005-03-08 19:26     ` Dave Anderson
2005-03-08 18:00 ` Eric W. Biederman
2005-03-09  6:43   ` Vivek Goyal
2005-03-09 14:17     ` [Fastboot] " Eric W. Biederman
2005-03-09 15:06       ` Dipankar Sarma
2005-03-10  7:11         ` Eric W. Biederman
2005-03-10  5:02       ` Vivek Goyal
2005-03-10  6:56         ` Eric W. Biederman
2005-03-15  5:49           ` Vivek Goyal
2005-03-10  8:16         ` Itsuro Oda
2005-03-09  6:57 ` Itsuro Oda
2005-03-23  4:26 ` Fernando Luis Vazquez Cao
2005-03-23 10:36   ` Vivek Goyal
2005-03-23 19:54     ` Eric W. Biederman [this message]
2005-03-23 19:47   ` [Fastboot] " Eric W. Biederman
     [not found]     ` <200503300258.34239.mark.williamson@cl.cam.ac.uk>
2005-03-30  7:42       ` 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=m18y4ervdu.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=fastboot@lists.osdl.org \
    --cc=fernando@intellilink.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@in.ibm.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