From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
KVM list <kvm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Oleg Nesterov <oleg@redhat.com>
Subject: qemu core dump and filtering guest pages
Date: Tue, 22 May 2012 23:05:57 +0200 [thread overview]
Message-ID: <4FBBFFB5.3010605@de.ibm.com> (raw)
Folks,
today we discussed the situation of a qemu crash (with coredump) and big guests.
Quite often the guest pages are not needed but make the core file pretty big.
The most appealing proposal that we had was to adopt the core file code in the
kernel to have an option for discarding guest pages (e.g. /proc/sys/core_guest).
do_corefile would have a callback into the kvm module that could use its memory
slot infrastructure to decide if this page should be saved or not.
Would you consider such a change be ok? Any better idea?
Thanks
Christian
next reply other threads:[~2012-05-22 21:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 21:05 Christian Borntraeger [this message]
2012-05-23 8:37 ` qemu core dump and filtering guest pages Avi Kivity
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=4FBBFFB5.3010605@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=oleg@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox