From: David Vrabel <david.vrabel@citrix.com>
To: Ross Lagerwall <ross.lagerwall@citrix.com>,
xen-devel@lists.xenproject.org
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
David Vrabel <david.vrabel@citrix.com>
Subject: Re: [PATCH] x86/xen: Warn when there's no mfn for pfn
Date: Thu, 2 Apr 2015 10:00:54 +0100 [thread overview]
Message-ID: <551D0546.8040702@citrix.com> (raw)
In-Reply-To: <1427959690-4682-1-git-send-email-ross.lagerwall@citrix.com>
On 02/04/15 08:28, Ross Lagerwall wrote:
> I recently had to debug dom0 taking a fatal page fault and it would have
> been useful if it warned when creating a non-present pte if there's no
> mfn for a pfn.
This will trigger for ever PTE covering memory hotplugged by the balloon
driver, so I don't think we can take this.
David
> --- a/arch/x86/xen/mmu.c
> +++ b/arch/x86/xen/mmu.c
> @@ -397,6 +397,7 @@ static pteval_t pte_pfn_to_mfn(pteval_t val)
> * pte_mfn_to_pfn is asymmetric.
> */
> if (unlikely(mfn == INVALID_P2M_ENTRY)) {
> + printk(KERN_WARNING "No mfn for pfn %lx, creating non-present pte\n", pfn);
> mfn = 0;
> flags = 0;
> } else
>
next prev parent reply other threads:[~2015-04-02 9:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 7:28 [PATCH] x86/xen: Warn when there's no mfn for pfn Ross Lagerwall
2015-04-02 9:00 ` David Vrabel [this message]
2015-04-02 9:10 ` Ross Lagerwall
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=551D0546.8040702@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=ross.lagerwall@citrix.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.