From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH] xen pv-on-hvm: add pfn_is_ram helper for kdump
Date: Thu, 12 Jul 2012 10:21:25 -0400 [thread overview]
Message-ID: <20120712142125.GF5204@phenom.dumpdata.com> (raw)
In-Reply-To: <20120712142234.GA22009@aepfle.de>
On Thu, Jul 12, 2012 at 04:22:34PM +0200, Olaf Hering wrote:
> On Thu, Jul 12, Konrad Rzeszutek Wilk wrote:
>
> > On Thu, Jul 12, 2012 at 11:00:05AM +0200, Olaf Hering wrote:
> > > Register pfn_is_ram helper speed up reading /proc/vmcore in the kdump
> > > kernel. See commit message of 997c136f518c ("fs/proc/vmcore.c: add hook
> > > to read_from_oldmem() to check for non-ram pages") for details.
> >
> > What about the 'unregister_oldmem_pfn_is_ram' call? Should this
> > be implemented here as well?
>
> There is no need to unregister because PVonHVM is not going away during
> the lifetime of the guest.
>
> > > +#include <linux/crash_dump.h>
> >
> > Should this also have an #idef CONFIG_PROC_VMCORE?
> > Or is it going to compile OK without CONFIG_PROC_VMCORE defined?
>
> All includes are supposed to work without ifdefs in the code, which is
> the case also for crash_dump.h
OK.
>
> > > + * previous kernel. If the pfn is ballooned, handle it properly.
> >
> > . and by handle it properly you mean return -ENXIO?
>
> Return code 0 means its a ballooned page and needs special care,
> non-null means it has to be handled as a RAM page.
>
> If the hypervisor is too old (4.1 and earlier) it just means that in
> case of kdump it will just cause high load in dom0.
> In case of kexec it will mean that the new kernel will crash because it
> can not know which pfn is actually there.
>
> > > + * Returns 0 if the pfn is not backed by a RAM page.
> > > + */
> > > +static int xen_oldmem_pfn_is_ram(unsigned long pfn)
> > > +{
> > > + struct xen_hvm_get_mem_type a;
> >
> > Can you make this have already initialized values, like:
> >
> > struct xen_hvm_get_mem_type a = {
> > .domid = DOMID_SELF;
> > .pfn = pfn
> > };
>
> Yes.
>
> > Also is this hypercall new? Or has it been in existence for some time?
>
> Its new in 4.2, and was backported to 4.1.1 as well.
Can you include the c/s in git commit pls?
next prev parent reply other threads:[~2012-07-12 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1342083605-15371-1-git-send-email-olaf@aepfle.de>
2012-07-12 9:01 ` [PATCH] xen pv-on-hvm: add pfn_is_ram helper for kdump Olaf Hering
2012-07-12 13:47 ` [Xen-devel] " Konrad Rzeszutek Wilk
2012-07-12 14:22 ` Olaf Hering
2012-07-12 14:21 ` Konrad Rzeszutek Wilk [this message]
[not found] <1342113639-19728-1-git-send-email-olaf@aepfle.de>
2012-07-12 17:24 ` Konrad Rzeszutek Wilk
2012-07-12 17:44 ` 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=20120712142125.GF5204@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox