From: Petr Tesarik <ptesarik@suse.cz>
To: xen-devel@lists.xen.org
Subject: Dumpfile filtering and PGC_xxx flags
Date: Fri, 24 Aug 2012 14:50:13 +0200 [thread overview]
Message-ID: <201208241450.13698.ptesarik@suse.cz> (raw)
Hello folks,
I've been trying to add support for xen-4.0+ to makedumpfile (a utility that
can filter out some content from a kernel dump file). In particular, I'm now
struggling with implementing option "-X", which should filter out all domU
pages, but keep hypervisor internal data and dom0 pages. Unused pages (free
pages, broken pages, offlined pages, etc.) should also be filtered out,
because they are usually not needed for dump analysis.
I'm relying on the contents of frame_table to do the job, but I'm lost in the
hierarchy of PGC_xxx flags. My first naive idea was that I could keep pages
that have:
1. PGC_allocated and
2. the right owner (dom_xen, dom_io, or dom0).
But that doesn't include Xen internal structures. In fact, the page_info
structs for pages corresponding to Xen code and static data seem to be
completely unitialized (all zero).
Thanks for any advice,
Petr Tesarik
SUSE Linux
next reply other threads:[~2012-08-24 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 12:50 Petr Tesarik [this message]
2012-08-24 22:48 ` Dumpfile filtering and PGC_xxx flags 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=201208241450.13698.ptesarik@suse.cz \
--to=ptesarik@suse.cz \
--cc=xen-devel@lists.xen.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 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.