From: Olaf Hering <olaf@aepfle.de>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>, mike.meyer@teradata.com
Subject: Re: [PATCH] unmodified_drivers: enable use of register_oldmem_pfn_is_ram() API
Date: Mon, 4 Apr 2016 13:20:52 +0200 [thread overview]
Message-ID: <20160404112052.GA4297@aepfle.de> (raw)
In-Reply-To: <5702645B02000078000E2A40@prv-mh.provo.novell.com>
On Mon, Apr 04, Jan Beulich wrote:
> From: Mike Meyer <mike.meyer@teradata.com>
>
> During the investigation of very slow dump times of guest images in
> Amazon EC2 instance, it was discovered that the
> register_oldmem_pfn_is_ram() API implemented by the upstream kernel
> commit 997c136f518c5debd63847e78e2a8694f56dcf90:
>
> fs/proc/vmcore.c: add hook to read_from_oldmem() to check
> for non-ram pages
>
> was not being called. This was due to the PV driver with the call
> to register_oldmem_pfn_is_ram() API was not including the
> kernel header file that is used to communicate support of the API in the
> kernel. Fix the issue by including the required header file.
>
> Signed-off-by: Mike Meyer <mike.meyer@teradata.com>
> Reviewed-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Olaf Hering <olaf@aepfle.de>
I'm sure I have tested it at that time, not sure why it used to work a
few years ago.
Olaf
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-04-04 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 10:55 [PATCH] unmodified_drivers: enable use of register_oldmem_pfn_is_ram() API Jan Beulich
2016-04-04 11:20 ` Olaf Hering [this message]
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=20160404112052.GA4297@aepfle.de \
--to=olaf@aepfle.de \
--cc=JBeulich@suse.com \
--cc=mike.meyer@teradata.com \
--cc=xen-devel@lists.xenproject.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.