[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <565434F102000078000B8424@prv-mh.provo.novell.com>
Date: Tue, 24 Nov 2015 01:59:13 -0700
From: "Jan Beulich" <JBeulich@...e.com>
To: "Daniel Kiper" <daniel.kiper@...cle.com>,
"Juergen Gross" <JGross@...e.com>
Cc: <olaf@...fle.de>, <andrew.cooper3@...rix.com>,
<david.vrabel@...rix.com>, <xen-devel@...ts.xenproject.org>,
<boris.ostrovsky@...cle.com>, <konrad.wilk@...cle.com>,
<anderson@...hat.com>, <crash-utility@...hat.com>,
"David Mair" <DMAIR@...e.com>, <ptesarik@...e.cz>,
<dslutz@...izon.com>, <linux-kernel@...r.kernel.org>,
<keir@....org>
Subject: Re: crash tool - problem with new Xen linear virtual mapped
sparse p2m list
>>> On 24.11.15 at 07:55, <JGross@...e.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.)
Jan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists