All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: Isaku Yamahata <yamahata@valinux.co.jp>, xen-devel@lists.xensource.com
Cc: John Levon <levon@movementarian.org>,
	Dave Anderson <anderson@redhat.com>,
	xen-ia64-devel@lists.xensource.com
Subject: Re: [PATCH 0/2] dump-core take 3
Date: Sun, 21 Jan 2007 10:05:42 +0000	[thread overview]
Message-ID: <C1D8EB76.78F2%keir@xensource.com> (raw)
In-Reply-To: <20070121074652.23834.28219.sendpatchset@ls.local.valinux.co.jp>

On 21/1/07 7:46 am, "Isaku Yamahata" <yamahata@valinux.co.jp> wrote:

> The following patchset is the dump-core take 3.
> It changes its format into ELF, adds PFN-GMFN table, HVM support,
> and adds IA64 preliminary chages.

These patches look much better.

Can you give some description of your Elf format? If we plan to use Elf for
save/restore as well, it would be nice to pick a format that is
generalisable to both cases. The use of program headers seems weird (since
there is no sensible 'virtual address' to specify, as the Xen core dump
format is not defined in the context of a simple single address space) and
is going to be no use for live migration where we need to be able to specify
GPFN-GMFN relationships on the fly, presumably in a custom section format.

Are there any tools to parse this new dump format, or will we have to wait
for the crash utility and xc_ptrace_core() to catch up?

 -- Keir

  parent reply	other threads:[~2007-01-21 10:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-21  7:46 [PATCH 0/2] dump-core take 3 Isaku Yamahata
2007-01-21  7:46 ` [PATCH 1/2] dump-core take 3: hvm domain: set shared_info.arch.max_pfn Isaku Yamahata
2007-01-21  7:47 ` [PATCH 2/2] dump-core take 3: elf formatify and added PFN-GMFN table Isaku Yamahata
2007-01-21 10:05 ` Keir Fraser [this message]
2007-01-21 14:02   ` [Xen-devel] [PATCH 0/2] dump-core take 3 Isaku Yamahata
2007-01-21 15:28     ` Keir Fraser
2007-01-21 16:23       ` [Xen-devel] " Isaku Yamahata
2007-01-22 16:10         ` Ian Campbell

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=C1D8EB76.78F2%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=anderson@redhat.com \
    --cc=levon@movementarian.org \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-ia64-devel@lists.xensource.com \
    --cc=yamahata@valinux.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.