From: Keir Fraser <keir@xensource.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
Keir Fraser <keir@xensource.com>,
John Levon <levon@movementarian.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: xc_get_pfn_list() creates broken core files
Date: Thu, 23 Nov 2006 19:05:08 +0000 [thread overview]
Message-ID: <C18BA164.4C17%keir@xensource.com> (raw)
In-Reply-To: <8A87A9A84C201449A0C56B728ACF491E01F981@liverpoolst.ad.cl.cam.ac.uk>
On 23/11/06 6:53 pm, "Ian Pratt" <m+Ian.Pratt@cl.cam.ac.uk> wrote:
>> Pagetables etc. are all in 'p' address space, so there should
>> be no need for p2m or m2p in that case I think
>>
>> In fact pagetables could be canonicalised into 'p' space for
>> PV guests too (xc_linux_save has the code for this) then
>> there'd be no need to dump the p2m table in the core dump at
>> all. Save format and core dump format should probably be one
>> and the same!
>
> Trouble is, the PV guest hasn't done an orderly suspend, and may be
> holding machine address references in registers/memory and in pagetables
> that haven't been pinned yet.
>
> The guest's core dump will already contain the p2m table, and its root
> location has been registered with xen during boot, so this just needs to
> be saved too.
It's questionable how useful the ability to m2p-translate those marginally
possible bits of state is though. Currently the p2m table is used *only* to
construct an m2p table allowing pagetable walks in xc_ptrace_core().
-- Keir
next prev parent reply other threads:[~2006-11-23 19:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-23 18:53 xc_get_pfn_list() creates broken core files Ian Pratt
2006-11-23 19:05 ` Keir Fraser [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-23 2:45 John Levon
2006-11-23 8:52 ` Keir Fraser
2006-11-23 18:16 ` John Levon
2006-11-23 18:39 ` Keir Fraser
2006-11-23 19:17 ` John Levon
2006-11-23 19:20 ` Keir Fraser
2006-11-23 20:52 ` John Levon
2006-11-23 22:05 ` John Levon
2006-11-25 16:03 ` Jimi Xenidis
2006-11-23 23:33 ` Keir Fraser
2006-11-23 23:48 ` John Levon
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=C18BA164.4C17%keir@xensource.com \
--to=keir@xensource.com \
--cc=levon@movementarian.org \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.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 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.