linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
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.comlinux-mm, @kvack.org
Cc: Juergen Gross <jgross@suse.com>
Subject: [Patch V3 07/15] xen: check memory area against e820 map
Date: Mon, 20 Apr 2015 07:23:32 +0200	[thread overview]
Message-ID: <1429507420-18201-8-git-send-email-jgross@suse.com> (raw)
In-Reply-To: <1429507420-18201-1-git-send-email-jgross@suse.com>

Provide a service routine to check a physical memory area against the
E820 map. The routine will return false if the complete area is RAM
according to the E820 map and true otherwise.

Signed-off-by: Juergen Gross <jgross@suse.com>
Reviewed-by: David Vrabel <david.vrabel@citrix.com>
---
 arch/x86/xen/setup.c   | 23 +++++++++++++++++++++++
 arch/x86/xen/xen-ops.h |  1 +
 2 files changed, 24 insertions(+)

diff --git a/arch/x86/xen/setup.c b/arch/x86/xen/setup.c
index 87251b4..99ef82c 100644
--- a/arch/x86/xen/setup.c
+++ b/arch/x86/xen/setup.c
@@ -573,6 +573,29 @@ static unsigned long __init xen_count_remap_pages(unsigned long max_pfn)
 	return extra;
 }
 
+bool __init xen_is_e820_reserved(phys_addr_t start, phys_addr_t size)
+{
+	struct e820entry *entry;
+	unsigned mapcnt;
+	phys_addr_t end;
+
+	if (!size)
+		return false;
+
+	end = start + size;
+	entry = xen_e820_map;
+
+	for (mapcnt = 0; mapcnt < xen_e820_map_entries; mapcnt++) {
+		if (entry->type == E820_RAM && entry->addr <= start &&
+		    (entry->addr + entry->size) >= end)
+			return false;
+
+		entry++;
+	}
+
+	return true;
+}
+
 /*
  * Reserve Xen mfn_list.
  * See comment above "struct start_info" in <xen/interface/xen.h>
diff --git a/arch/x86/xen/xen-ops.h b/arch/x86/xen/xen-ops.h
index 9e195c6..c1385b8 100644
--- a/arch/x86/xen/xen-ops.h
+++ b/arch/x86/xen/xen-ops.h
@@ -39,6 +39,7 @@ void xen_reserve_top(void);
 void xen_mm_pin_all(void);
 void xen_mm_unpin_all(void);
 
+bool __init xen_is_e820_reserved(phys_addr_t start, phys_addr_t size);
 unsigned long __ref xen_chk_extra_mem(unsigned long pfn);
 void __init xen_inv_extra_mem(void);
 void __init xen_remap_memory(void);
-- 
2.1.4

  parent reply	other threads:[~2015-04-20  5:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20  5:23 [Patch V3 00/15] xen: support pv-domains larger than 512GB Juergen Gross
2015-04-20  5:23 ` [Patch V3 01/15] xen: sync with xen headers Juergen Gross
2015-04-20  5:23 ` [Patch V3 02/15] xen: save linear p2m list address in shared info structure Juergen Gross
2015-04-20  5:23 ` [Patch V3 03/15] xen: don't build mfn tree if tools don't need it Juergen Gross
2015-04-20  5:23 ` [Patch V3 04/15] xen: eliminate scalability issues from initial mapping setup Juergen Gross
2015-04-20  5:23 ` [Patch V3 05/15] xen: move static e820 map to global scope Juergen Gross
2015-04-20  5:23 ` [Patch V3 06/15] xen: split counting of extra memory pages from remapping Juergen Gross
2015-04-20  5:23 ` Juergen Gross [this message]
2015-04-20  5:23 ` [Patch V3 08/15] xen: find unused contiguous memory area Juergen Gross
2015-04-20  5:23 ` [Patch V3 09/15] xen: check for kernel memory conflicting with memory layout Juergen Gross
2015-04-20  5:23 ` [Patch V3 10/15] xen: check pre-allocated page tables for conflict with memory map Juergen Gross
2015-04-20  5:23 ` [Patch V3 11/15] xen: check for initrd conflicting with e820 map Juergen Gross
2015-04-20  5:23 ` [Patch V3 12/15] mm: provide early_memremap_ro to establish read-only mapping Juergen Gross
2015-04-20  5:23 ` [Patch V3 13/15] xen: move p2m list if conflicting with e820 map Juergen Gross
2015-04-20  5:23 ` [Patch V3 14/15] xen: allow more than 512 GB of RAM for 64 bit pv-domains Juergen Gross
2015-04-20  5:23 ` [Patch V3 15/15] xen: remove no longer needed p2m.h Juergen Gross

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=1429507420-18201-8-git-send-email-jgross@suse.com \
    --to=jgross@suse.com \
    --cc=boris.ostrovsky@oracle.comlinux-mm \
    --cc=david.vrabel@citrix.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;
as well as URLs for NNTP newsgroup(s).