From: Daniel Kiper <daniel.kiper@oracle.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: crash-utility@redhat.com, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
jgross@suse.com, olaf@aepfle.de, keir@xen.org,
andrew.cooper3@citrix.com, ptesarik@suse.cz, dslutz@verizon.com,
anderson@redhat.com, dmair@suse.com, boris.ostrovsky@oracle.com
Subject: Re: [Xen-devel] [PATCH] xen: Add support for dom0 with Linux kernel 3.19 and newer
Date: Fri, 22 Jan 2016 15:22:06 +0100 [thread overview]
Message-ID: <20160122142206.GZ3485@olila.local.net-space.pl> (raw)
In-Reply-To: <56A1FE76.40201@citrix.com>
On Fri, Jan 22, 2016 at 10:03:34AM +0000, David Vrabel wrote:
> On 21/01/16 20:13, Daniel Kiper wrote:
> > Linux kernel commit 054954eb051f35e74b75a566a96fe756015352c8
> > (xen: switch to linear virtual mapped sparse p2m list), which
> > appeared in 3.19, introduced linear virtual mapped sparse p2m
> > list. If readmem() reads p2m then it access this list using
> > physical addresses. Sadly, VMA to physical address translation
> > in crash requires access to p2m list. This means that we have
> > a chicken and egg problem. In general this issue must be solved
> > by introducing some changes in libxl, Linux kernel and crash
> > (I have added this task to my long TODO list). However, in dom0
> > case we can use crash_xen_info_t.dom0_pfn_to_mfn_frame_list_list
> > which is available out of the box. So, let's use it and make
> > at least some users happy.
>
> I'm confused. How does a virtual address to (pseudo-)physical address
> lookup require access to the p2m? Surely this is a walk of the page
> tables followed by a M2P lookup on the MFN in the L1 PTE?
Correct but crash does it a bit backward and scans p2m. I am not sure way,
however, I am going to look at it during work on PV guests support.
Daniel
prev parent reply other threads:[~2016-01-22 14:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 20:13 Daniel Kiper
2016-01-22 10:03 ` [Xen-devel] " David Vrabel
2016-01-22 14:22 ` Daniel Kiper [this message]
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=20160122142206.GZ3485@olila.local.net-space.pl \
--to=daniel.kiper@oracle.com \
--cc=anderson@redhat.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=crash-utility@redhat.com \
--cc=david.vrabel@citrix.com \
--cc=dmair@suse.com \
--cc=dslutz@verizon.com \
--cc=jgross@suse.com \
--cc=keir@xen.org \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®