[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56543412.7090104@citrix.com>
Date: Tue, 24 Nov 2015 09:55:30 +0000
From: Malcolm Crossley <malcolm.crossley@...rix.com>
To: Jan Beulich <JBeulich@...e.com>,
Daniel Kiper <daniel.kiper@...cle.com>,
Juergen Gross <JGross@...e.com>
CC: <olaf@...fle.de>, <keir@....org>, <andrew.cooper3@...rix.com>,
<ptesarik@...e.cz>, <linux-kernel@...r.kernel.org>,
<dslutz@...izon.com>, <anderson@...hat.com>,
<david.vrabel@...rix.com>, David Mair <DMAIR@...e.com>,
<xen-devel@...ts.xenproject.org>, <boris.ostrovsky@...cle.com>,
<crash-utility@...hat.com>
Subject: Re: [Xen-devel] crash tool - problem with new Xen linear virtual
mapped sparse p2m list
On 24/11/15 08:59, Jan Beulich wrote:
>>>> 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.)
>
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.
Malcolm
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@...ts.xen.org
> http://lists.xen.org/xen-devel
>
--
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