From: Olaf Hering <olaf@aepfle.de>
To: Jan Beulich <JBeulich@novell.com>
Cc: xen-devel@lists.xensource.com, Tim Deegan <Tim.Deegan@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [PATCH 0 of 5] update xenctx to dump pagetables
Date: Wed, 22 Jun 2011 15:50:34 +0200 [thread overview]
Message-ID: <20110622135034.GA9924@aepfle.de> (raw)
In-Reply-To: <4E008F1D02000078000487E9@nat28.tlf.novell.com>
On Tue, Jun 21, Jan Beulich wrote:
> >>> On 21.06.11 at 11:59, Tim Deegan <Tim.Deegan@citrix.com> wrote:
> > Hi,
> >
> > At 17:56 -0400 on 20 Jun (1308592583), Konrad Rzeszutek Wilk wrote:
> >> > Any ideas why some mfns are not accessible?
> >>
> >> They look to be the special I/O PFNs. The ones that cover ACPI, framebuffer,
> >> PCI IO bars, MP tale.
> >
> > I think they're too high for that, but if you can post the e820 map of
> > the system this happened on then we'll know.
> >
> >> > Are there any other paging states maintained outside of the guests
> >> > memory?
> >>
> >> They look to be I/O pages.
> >>
> >> But not sure why they are mapped to your guest?
> >
> > But they're not mapped into the guest - from the look of them they're
> > not mapped anywhere. You could add some extra printouts around that
> > warning in mm.c to show whether the MFNs are valid and if so which
> > domain owns them.
> >
> > Also, interesting that it's the addresses just above 0xffff800000000000
> > that are different - what lives at that address in the PV kernel you're
> > running?
>
> That's Xen's space, isn't it. Clearly any non-hypervisor based page
> table walking code has to ignore this range for PV guests' page
> tables.
Is there a way to detect that? I cant seem to match any of these ranges to
something in guests dmesg or /proc.
After adding some debug to my xenctx from sles11 4.0, I get this on vcpu 0:
xc_map_foreign_range: walk_l3: 0 virt 0000800000000000 mfn 13fff8: Invalid argument
xc_map_foreign_range: walk_l3: 0 virt 0000808000000000 mfn 13fff0: Invalid argument
xc_map_foreign_range: walk_l2: 0 virt 0000814000000000 mfn 13fff8: Invalid argument
xc_map_foreign_range: walk_l2: 0 virt 0000814040000000 mfn 13fff0: Invalid argument
xc_map_foreign_range: walk_l1: 0 virt 00008140a0000000 mfn 13fff8: Invalid argument
xc_map_foreign_range: walk_l1: 0 virt 00008140a0200000 mfn 13fff0: Invalid argument
xc_map_foreign_range: walk_l1: 0 virt 00008140a0800000 mfn 137ff8: Invalid argument
xc_map_foreign_range: walk_l1: 0 virt 00008140a0a00000 mfn bf49a: Invalid argument
xc_map_foreign_range: walk_l1: 0 virt 00008140a0c00000 mfn bf495: Invalid argument
xc_map_foreign_range: walk_l2: 0 virt 0000814100000000 mfn 137ff8: Invalid argument
xc_map_foreign_range: walk_l2: 0 virt 0000814140000000 mfn bf49a: Invalid argument
xc_map_foreign_range: walk_l2: 0 virt 0000814180000000 mfn bf495: Invalid argument
xc_map_foreign_range: walk_l3: 0 virt 0000820000000000 mfn 137ff8: Invalid argument
xc_map_foreign_range: walk_l3: 0 virt 0000828000000000 mfn bf49a: Invalid argument
xc_map_foreign_range: walk_l3: 0 virt 0000830000000000 mfn bf495: Invalid argument
And dmesg has:
(XEN) mm.c:880:d0 Error getting mfn 13fff8 (pfn 5555555555555555) from L1 entry 800000013fff8625 for l1e_owner=0, pg_owner=1
(XEN) mm.c:880:d0 Error getting mfn 13fff0 (pfn 5555555555555555) from L1 entry 800000013fff0625 for l1e_owner=0, pg_owner=1
(XEN) mm.c:880:d0 Error getting mfn 13fff8 (pfn 5555555555555555) from L1 entry 800000013fff8625 for l1e_owner=0, pg_owner=1
(XEN) mm.c:880:d0 Error getting mfn 13fff0 (pfn 5555555555555555) from L1 entry 800000013fff0625 for l1e_owner=0, pg_owner=1
(XEN) mm.c:880:d0 Error getting mfn 13fff8 (pfn 5555555555555555) from L1 entry 800000013fff8625 for l1e_owner=0, pg_owner=1
(XEN) mm.c:880:d0 Error getting mfn 13fff0 (pfn 5555555555555555) from L1 entry 800000013fff0625 for l1e_owner=0, pg_owner=1
(XEN) mm.c:880:d0 Error getting mfn 137ff8 (pfn f180d) from L1 entry 8000000137ff8625 for l1e_owner=0, pg_owner=1
(XEN) mm.c:880:d0 Error getting mfn bf49a (pfn 5555555555555555) from L1 entry 80000000bf49a625 for l1e_owner=0, pg_owner=1
(XEN) mm.c:880:d0 Error getting mfn bf495 (pfn 5555555555555555) from L1 entry 80000000bf495625 for l1e_owner=0, pg_owner=1
(XEN) mm.c:880:d0 Error getting mfn 137ff8 (pfn f180d) from L1 entry 8000000137ff8625 for l1e_owner=0, pg_owner=1
(XEN) mm.c:880:d0 Error getting mfn bf49a (pfn 5555555555555555) from L1 entry 80000000bf49a625 for l1e_owner=0, pg_owner=1
(XEN) mm.c:880:d0 Error getting mfn bf495 (pfn 5555555555555555) from L1 entry 80000000bf495625 for l1e_owner=0, pg_owner=1
(XEN) mm.c:880:d0 Error getting mfn 137ff8 (pfn f180d) from L1 entry 8000000137ff8625 for l1e_owner=0, pg_owner=1
(XEN) mm.c:880:d0 Error getting mfn bf49a (pfn 5555555555555555) from L1 entry 80000000bf49a625 for l1e_owner=0, pg_owner=1
(XEN) mm.c:880:d0 Error getting mfn bf495 (pfn 5555555555555555) from L1 entry 80000000bf495625 for l1e_owner=0, pg_owner=1
Olaf
next prev parent reply other threads:[~2011-06-22 13:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 15:26 [PATCH 0 of 5] update xenctx to dump pagetables Olaf Hering
2011-06-20 15:26 ` [PATCH 1 of 5] xenctx: recognize also -S option for --stack-trace Olaf Hering
2011-06-20 15:26 ` [PATCH 2 of 5] xenctx: move all globals into struct xenctx Olaf Hering
2011-06-21 12:36 ` Ian Jackson
2011-06-21 15:27 ` Olaf Hering
2011-06-21 15:31 ` Ian Jackson
2011-06-20 15:26 ` [PATCH 3 of 5] xenctx: move xc_* access out of dump_ctx Olaf Hering
2011-06-20 15:27 ` [PATCH 4 of 5] xenctx: add option -C to dump context for all vcpus Olaf Hering
2011-06-20 15:27 ` [PATCH 5 of 5] xenctx: dump pagetable Olaf Hering
2011-06-21 12:33 ` Ian Jackson
2011-06-21 15:25 ` Olaf Hering
2011-06-20 17:33 ` [PATCH 0 of 5] update xenctx to dump pagetables Tim Deegan
2011-06-20 17:51 ` Olaf Hering
2011-06-20 21:56 ` Konrad Rzeszutek Wilk
2011-06-21 9:59 ` Tim Deegan
2011-06-21 10:31 ` Jan Beulich
2011-06-22 13:50 ` Olaf Hering [this message]
2011-06-22 14:34 ` 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=20110622135034.GA9924@aepfle.de \
--to=olaf@aepfle.de \
--cc=JBeulich@novell.com \
--cc=Tim.Deegan@citrix.com \
--cc=konrad.wilk@oracle.com \
--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.