From: David Vrabel <david.vrabel@citrix.com>
To: Malcolm Crossley <malcolm.crossley@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
Daniel Kiper <daniel.kiper@oracle.com>,
Juergen Gross <JGross@suse.com>
Cc: <olaf@aepfle.de>, <keir@xen.org>, <andrew.cooper3@citrix.com>,
<ptesarik@suse.cz>, <linux-kernel@vger.kernel.org>,
<dslutz@verizon.com>, <anderson@redhat.com>,
David Mair <DMAIR@suse.com>, <xen-devel@lists.xenproject.org>,
<boris.ostrovsky@oracle.com>, <crash-utility@redhat.com>
Subject: Re: [Xen-devel] crash tool - problem with new Xen linear virtual mapped sparse p2m list
Date: Tue, 24 Nov 2015 10:09:01 +0000 [thread overview]
Message-ID: <5654373D.9070403@citrix.com> (raw)
In-Reply-To: <56543412.7090104@citrix.com>
On 24/11/15 09:55, Malcolm Crossley wrote:
> On 24/11/15 08:59, Jan Beulich wrote:
>>>>> On 24.11.15 at 07:55, <JGross@suse.com> wrote:
>>> What about:
>>>
>>> 4) Instead of relying on the kernel maintained p2m list for m2p
>>> conversion use the hypervisor maintained m2p list which should be
>>> available in the dump as well. This is the way the alive kernel is
>>> working, so mimic it during crash dump analysis.
>>
>> I fully agree; I have to admit that looking at the p2m when doing page
>> table walks for a PV Dom0 (having all machine addresses in page table
>> entries) seems kind of backwards. (But I say this knowing nothing
>> about the tool.)
>>
> I don't think we can reliably use the m2p for PV domains because
> PV domains don't always issue a m2p update hypercall when they change
> their p2m mapping.
This only applies to foreign pages which won't be very interesting to a
crash tool.
David
next prev parent reply other threads:[~2015-11-24 10:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 20:18 crash tool - problem with new Xen linear virtual mapped sparse p2m list Daniel Kiper
2015-11-24 6:55 ` Juergen Gross
2015-11-24 8:59 ` Jan Beulich
2015-11-24 9:55 ` [Xen-devel] " Malcolm Crossley
2015-11-24 10:09 ` David Vrabel [this message]
2015-11-24 10:17 ` Petr Tesarik
2015-11-24 10:35 ` Andrew Cooper
2015-11-24 12:57 ` Petr Tesarik
2015-11-24 13:39 ` Jan Beulich
2015-11-24 13:41 ` Andrew Cooper
2015-11-24 13:42 ` Andrew Cooper
2015-11-24 13:46 ` Ian Campbell
2015-11-24 13:55 ` Jan Beulich
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=5654373D.9070403@citrix.com \
--to=david.vrabel@citrix.com \
--cc=DMAIR@suse.com \
--cc=JBeulich@suse.com \
--cc=JGross@suse.com \
--cc=anderson@redhat.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=crash-utility@redhat.com \
--cc=daniel.kiper@oracle.com \
--cc=dslutz@verizon.com \
--cc=keir@xen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=malcolm.crossley@citrix.com \
--cc=olaf@aepfle.de \
--cc=ptesarik@suse.cz \
--cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox