Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1628401 > unrolled thread

[PATCH v2] xen/pvh: Do not fill kernel's e820 map in init_pvh_bootparams()

Started byBoris Ostrovsky <boris.ostrovsky@oracle.com>
First post2017-04-21 19:50 +0200
Last post2017-04-24 18:10 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.kernel


Contents

  [PATCH v2] xen/pvh: Do not fill kernel's e820 map in init_pvh_bootparams() Boris Ostrovsky <boris.ostrovsky@oracle.com> - 2017-04-21 19:50 +0200
    Re: [PATCH v2] xen/pvh: Do not fill kernel's e820 map in  init_pvh_bootparams() Juergen Gross <jgross@suse.com> - 2017-04-24 18:10 +0200

#1628401 — [PATCH v2] xen/pvh: Do not fill kernel's e820 map in init_pvh_bootparams()

FromBoris Ostrovsky <boris.ostrovsky@oracle.com>
Date2017-04-21 19:50 +0200
Subject[PATCH v2] xen/pvh: Do not fill kernel's e820 map in init_pvh_bootparams()
Message-ID<tyKQW-gp-29@gated-at.bofh.it>
e820 map is updated with information from the zeropage (i.e. pvh_bootparams)
by default_machine_specific_memory_setup(). With the way things are done
now,  we end up with a duplicated e820 map.

Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
---
v2:
* Drop sanitize_e820_map() since it will be called later
  anyway, possibly more than once.
* Also use pvh_bootparams.e820_entries instead of memmap.nr_entries
  when adding ISA range.

 arch/x86/xen/enlighten_pvh.c | 22 ++++++----------------
 1 file changed, 6 insertions(+), 16 deletions(-)

diff --git a/arch/x86/xen/enlighten_pvh.c b/arch/x86/xen/enlighten_pvh.c
index 331d769..2bc7d5b 100644
--- a/arch/x86/xen/enlighten_pvh.c
+++ b/arch/x86/xen/enlighten_pvh.c
@@ -33,7 +33,6 @@ static void xen_pvh_arch_setup(void)
 static void __init init_pvh_bootparams(void)
 {
 	struct xen_memory_map memmap;
-	unsigned int i;
 	int rc;
 
 	memset(&pvh_bootparams, 0, sizeof(pvh_bootparams));
@@ -45,28 +44,19 @@ static void __init init_pvh_bootparams(void)
 		xen_raw_printk("XENMEM_memory_map failed (%d)\n", rc);
 		BUG();
 	}
+	pvh_bootparams.e820_entries = memmap.nr_entries;
 
-	if (memmap.nr_entries < E820MAX - 1) {
-		pvh_bootparams.e820_map[memmap.nr_entries].addr =
+	if (pvh_bootparams.e820_entries < E820MAX - 1) {
+		pvh_bootparams.e820_map[pvh_bootparams.e820_entries].addr =
 			ISA_START_ADDRESS;
-		pvh_bootparams.e820_map[memmap.nr_entries].size =
+		pvh_bootparams.e820_map[pvh_bootparams.e820_entries].size =
 			ISA_END_ADDRESS - ISA_START_ADDRESS;
-		pvh_bootparams.e820_map[memmap.nr_entries].type =
+		pvh_bootparams.e820_map[pvh_bootparams.e820_entries].type =
 			E820_RESERVED;
-		memmap.nr_entries++;
+		pvh_bootparams.e820_entries++;
 	} else
 		xen_raw_printk("Warning: Can fit ISA range into e820\n");
 
-	sanitize_e820_map(pvh_bootparams.e820_map,
-			  ARRAY_SIZE(pvh_bootparams.e820_map),
-			  &memmap.nr_entries);
-
-	pvh_bootparams.e820_entries = memmap.nr_entries;
-	for (i = 0; i < pvh_bootparams.e820_entries; i++)
-		e820_add_region(pvh_bootparams.e820_map[i].addr,
-				pvh_bootparams.e820_map[i].size,
-				pvh_bootparams.e820_map[i].type);
-
 	pvh_bootparams.hdr.cmd_line_ptr =
 		pvh_start_info.cmdline_paddr;
 
-- 
2.9.3

[toc] | [next] | [standalone]


#1629719 — Re: [PATCH v2] xen/pvh: Do not fill kernel's e820 map in init_pvh_bootparams()

FromJuergen Gross <jgross@suse.com>
Date2017-04-24 18:10 +0200
SubjectRe: [PATCH v2] xen/pvh: Do not fill kernel's e820 map in init_pvh_bootparams()
Message-ID<tzOIO-JE-9@gated-at.bofh.it>
In reply to#1628401
On 21/04/17 17:13, Boris Ostrovsky wrote:
> e820 map is updated with information from the zeropage (i.e. pvh_bootparams)
> by default_machine_specific_memory_setup(). With the way things are done
> now,  we end up with a duplicated e820 map.
> 
> Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>

Reviewed-by: Juergen Gross <jgross@suse.com>


Juergen

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web