From: Olaf Hering <olaf@aepfle.de>
To: xen-devel@lists.xensource.com
Subject: audit_p2m errors, p2m_mmio_direct turns into p2m_ram_logdirty
Date: Tue, 2 Nov 2010 17:54:29 +0100 [thread overview]
Message-ID: <20101102165429.GA30730@aepfle.de> (raw)
Hello,
audit_p2m appears to be unmaintained, given that it did not even compile
up to a few weeks ago (and it still does not compile in 4.0 tree).
Today I tried it again in the hope to get some help for xenpaging
debugging in xen-4.0, but it ran into a BUG right away.
For some reason the p2m type set by set_mmio_p2m_entry for gfn 0xfee00
is 2 instead of 5 when audit_p2m checks it.
How can the BUG get fixed properly?
(I turned all P2M_PRINTK into printk, and dumped the p2mt in a few
places):
(XEN) p2m: p2m_alloc_table(1645): allocating p2m table
(XEN) p2m: p2m_alloc_table(1669): populating p2m table
(XEN) p2m: p2m_alloc_table(1697): p2m table initialised (0 pages)
(XEN) p2mdebug: set_mmio_p2m_entry(2399): set mmio fee00 134012
(XEN) cpupool_add_domain(dom=1,pool=0) n_dom 2
(XEN) p2m: audit_p2m(1762): p2m audit starts
(XEN) p2m: audit_p2m(1777): auditing guest page, mfn=0x133b86
(XEN) p2m: audit_p2m(1821): map mismatch mfn 0x133b86 -> gfn 0xed47f -> mfn 0xffffffffffffffff (-> gfn 0xffffffff) p2mt 4
(XEN) p2m: audit_p2m(1839): OK: mfn=0x133b86, gfn=0xed47f, p2mfn=0xffffffffffffffff, lp2mfn=0x0
(XEN) p2m: audit_p2m(1941): mismatch: gfn 0xfee00 -> mfn 0x134012 -> gfn 0xffffffffffffffff (p2mt 2)
(XEN) Xen BUG at p2m.c:1942
(XEN) Debugging connection not set up.
Olaf
next reply other threads:[~2010-11-02 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 16:54 Olaf Hering [this message]
2010-11-03 12:12 ` audit_p2m errors, p2m_mmio_direct turns into p2m_ram_logdirty Tim Deegan
2010-11-03 13:59 ` Olaf Hering
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=20101102165429.GA30730@aepfle.de \
--to=olaf@aepfle.de \
--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.