From: Petr Tesarik <ptesarik@suse.cz>
To: Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>
Cc: kexec@lists.infradead.org
Subject: [PATCH 0/2] Allow Xen Dom0 page filtering
Date: Thu, 27 Mar 2014 18:49:40 +0100 [thread overview]
Message-ID: <20140327175508.5F86560141@nathan.suse.cz> (raw)
Trying to use makedumpfile on a Xen Dom0 ELF file currently fails, but there
are in fact only a few missing pieces. With the following two patches, I was
able to produce a dump even with high dump levels (-d17 and -d31).
Needless to say, this can reduce the size of Dom0 dumps considerably.
Petr Tesarik (2):
Earlier initialization of dom0_mapnr
Get Dom0 max_pfn using pfn_mfn_frame_list if max_pfn unavailable
makedumpfile.c | 35 ++++++++++++++++++++++++++++-------
1 file changed, 28 insertions(+), 7 deletions(-)
--
1.8.4.5
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2014-03-27 17:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 17:49 Petr Tesarik [this message]
2014-03-27 18:06 ` [PATCH 0/2] Allow Xen Dom0 page filtering Petr Tesarik
2014-03-27 18:06 ` [PATCH 1/2] Earlier initialization of dom0_mapnr Petr Tesarik
2014-03-28 8:18 ` Atsushi Kumagai
2014-03-28 8:26 ` Petr Tesarik
2014-03-28 9:01 ` Atsushi Kumagai
2014-03-28 12:08 ` [PATCH v2 0/2] Allow Xen Dom0 page filtering Petr Tesarik
2014-03-28 12:08 ` [PATCH v2 1/2] Earlier initialization of dom0_mapnr Petr Tesarik
2014-03-28 12:08 ` [PATCH v2 2/2] Get Dom0 max_pfn using pfn_mfn_frame_list if max_pfn unavailable Petr Tesarik
2014-03-28 12:08 ` [PATCH 0/2] Allow Xen Dom0 page filtering Petr Tesarik
2014-04-03 2:38 ` [PATCH v2 " Atsushi Kumagai
2014-03-28 12:09 ` Petr Tesarik
2014-03-28 12:09 ` [PATCH v2 1/2] Earlier initialization of dom0_mapnr Petr Tesarik
2014-03-28 12:09 ` [PATCH v2 2/2] Get Dom0 max_pfn using pfn_mfn_frame_list if max_pfn unavailable Petr Tesarik
2014-03-27 18:06 ` [PATCH " Petr Tesarik
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=20140327175508.5F86560141@nathan.suse.cz \
--to=ptesarik@suse.cz \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
/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