From: Juergen Gross <jgross@suse.com>
To: linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
konrad.wilk@oracle.com, david.vrabel@citrix.com,
boris.ostrovsky@oracle.com, jbeulich@suse.com
Cc: Juergen Gross <jgross@suse.com>
Subject: [Patch V2 4/4] xen: check for zero sized area when invalidating memory
Date: Mon, 12 Jan 2015 06:05:10 +0100 [thread overview]
Message-ID: <1421039110-11207-5-git-send-email-jgross@suse.com> (raw)
In-Reply-To: <1421039110-11207-1-git-send-email-jgross@suse.com>
With the introduction of the linear mapped p2m list setting memory
areas to "invalid" had to be delayed. When doing the invalidation
make sure no zero sized areas are processed.
Signed-off-by: Juegren Gross <jgross@suse.com>
---
arch/x86/xen/setup.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/x86/xen/setup.c b/arch/x86/xen/setup.c
index 410210f..865e56c 100644
--- a/arch/x86/xen/setup.c
+++ b/arch/x86/xen/setup.c
@@ -160,6 +160,8 @@ void __init xen_inv_extra_mem(void)
int i;
for (i = 0; i < XEN_EXTRA_MEM_MAX_REGIONS; i++) {
+ if (!xen_extra_mem[i].size)
+ continue;
pfn_s = PFN_DOWN(xen_extra_mem[i].start);
pfn_e = PFN_UP(xen_extra_mem[i].start + xen_extra_mem[i].size);
for (pfn = pfn_s; pfn < pfn_e; pfn++)
--
2.1.2
next prev parent reply other threads:[~2015-01-12 5:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 5:05 [Patch V2 0/4] xen: correct several bugs in new p2m list setup Juergen Gross
2015-01-12 5:05 ` [Patch V2 1/4] xen: correct error for building p2m list on 32 bits Juergen Gross
2015-01-12 5:05 ` [Patch V2 2/4] xen: correct race in alloc_p2m_pmd() Juergen Gross
2015-01-12 5:05 ` [Patch V2 3/4] xen: use correct type for physical addresses Juergen Gross
2015-01-12 5:05 ` Juergen Gross [this message]
2015-01-12 11:10 ` [Xen-devel] [Patch V2 0/4] xen: correct several bugs in new p2m list setup David Vrabel
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=1421039110-11207-5-git-send-email-jgross@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=jbeulich@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome