linux-um archives
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: user-mode-linux-devel@lists.sourceforge.net,
	lkml <linux-kernel@vger.kernel.org>
Subject: [uml-devel] Re: Another bug report for UML in latest Linux 2.6-BK repository.
Date: Wed, 17 Nov 2004 00:45:26 -0500	[thread overview]
Message-ID: <200411170545.iAH5jQm7007146@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Tue, 16 Nov 2004 13:41:11 GMT." <1100612471.24599.42.camel@imp.csi.cam.ac.uk>

aia21@cam.ac.uk said:
> If I enable HIGHMEM in my .config (see my previous bug report for my
> .config and just change HIGHMEM to enabled) compilation fails: 

The patch below fixes it.

				Jeff

Index: 2.6.9/arch/um/Kconfig
===================================================================
--- 2.6.9.orig/arch/um/Kconfig	2004-11-16 21:25:38.000000000 -0500
+++ 2.6.9/arch/um/Kconfig	2004-11-16 21:44:53.000000000 -0500
@@ -224,7 +224,15 @@
 
 config HIGHMEM
 	bool "Highmem support"
-	depends on BROKEN
+	default n
+	help
+	This enables UML's highmem support.  This allows UML to have
+	more physical memory than it can map into its virtual address
+	space.  In tt mode, or with CONFIG_MODE_TT enabled, the limit is a
+	bit less than 512M.  With CONFIG_MODE_TT disabled and
+	CONFIG_LOAD_LOW and CONFIG_STATIC_LINK enabled, the limit is
+	around 2.75G.
+	Enabling this option slows down UML, signficantly in skas mode.
 
 config KERNEL_STACK_ORDER
 	int "Kernel stack size order"
Index: 2.6.9/arch/um/kernel/mem.c
===================================================================
--- 2.6.9.orig/arch/um/kernel/mem.c	2004-11-16 21:54:53.000000000 -0500
+++ 2.6.9/arch/um/kernel/mem.c	2004-11-16 21:55:45.000000000 -0500
@@ -68,7 +68,7 @@
 
 	max_low_pfn = (high_physmem - uml_physmem) >> PAGE_SHIFT;
 #ifdef CONFIG_HIGHMEM
-	highmem_start_page = phys_page(__pa(high_physmem));
+	highmem_start_page = pfn_to_page(phys_to_pfn(__pa(high_physmem)));
 #endif
 
         /* clear the zero-page */
@@ -140,7 +140,7 @@
 pgprot_t kmap_prot;
 
 #define kmap_get_fixmap_pte(vaddr)					\
-	pte_offset_kernel(pmd_offset(pml4_pgd_offset(pml4_offset_k(vaddr),
+	pte_offset_kernel(pmd_offset(pml4_pgd_offset(pml4_offset_k(vaddr), \
 						     vaddr), (vaddr)), (vaddr))
 
 void __init kmap_init(void)



-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

      reply	other threads:[~2004-11-17  3:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-16 13:41 [uml-devel] Another bug report for UML in latest Linux 2.6-BK repository Anton Altaparmakov
2004-11-17  5:45 ` Jeff Dike [this message]

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=200411170545.iAH5jQm7007146@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=aia21@cam.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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