From: "Christoph Egger" <Christoph.Egger@amd.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH][XEN] construct_dom0: Initialize variable before use
Date: Thu, 29 Nov 2007 14:02:13 +0100 [thread overview]
Message-ID: <200711291402.14214.Christoph.Egger@amd.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]
Hi!
Attached patch initializes d->arch.physaddr_bitsize properly for a
64bit Dom0/64bit hypervisor.
This bug has been found when booting a NetBSD/Xen Dom0 with more
than 4GB RAM.
Without this fix, d->arch.physaddr_bitsize is 0 in
domain_clamp_alloc_bitsize(). This causes all attempts to
XENMEM_increase_reservation with bits > 0 to fail. More precisely,
__alloc_domheap_pages() returns NULL.
This impacts Xen heap allocation in general.
Question: How did that work on Linux Dom0?
I think, initializing physaddr_bitsize to 64 unconditionally is ok because in
construct_dom0() it is overridden with the proper value when you boot
64bit hypervisor with a 32bit Dom0. If the hypervisor is not 64bit,
physaddr_bitsize isn't used at all anyway.
Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
--
AMD Saxony, Dresden, Germany
Operating System Research Center
Legal Information:
AMD Saxony Limited Liability Company & Co. KG
Sitz (Geschäftsanschrift):
Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland
Registergericht Dresden: HRA 4896
vertretungsberechtigter Komplementär:
AMD Saxony LLC (Sitz Wilmington, Delaware, USA)
Geschäftsführer der AMD Saxony LLC:
Dr. Hans-R. Deppe, Thomas McCoy
[-- Attachment #2: xen_dom0.diff --]
[-- Type: text/plain, Size: 629 bytes --]
diff -r 6fd17d0dcbcd xen/arch/x86/domain_build.c
--- a/xen/arch/x86/domain_build.c Tue Nov 27 12:49:16 2007 +0000
+++ b/xen/arch/x86/domain_build.c Wed Nov 28 17:37:53 2007 +0100
@@ -353,6 +353,11 @@ int __init construct_dom0(
if ( parms.pae == PAEKERN_extended_cr3 )
set_bit(VMASST_TYPE_pae_extended_cr3, &d->vm_assist);
+ /* Unconditionally initialize this member here for 64bit Dom0s.
+ * In the below if (), this is overridden for 32bit Dom0s.
+ */
+ d->arch.physaddr_bitsize = 64;
+
if ( UNSET_ADDR != parms.virt_hv_start_low && elf_32bit(&elf) )
{
#if CONFIG_PAGING_LEVELS < 4
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2007-11-29 13:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 13:02 Christoph Egger [this message]
2007-11-29 13:28 ` [PATCH][XEN] construct_dom0: Initialize variable before use Keir Fraser
2007-11-29 13:37 ` Christoph Egger
2007-11-29 14:32 ` Christoph Egger
2007-11-29 14:34 ` Keir Fraser
[not found] <C37DAC27.197BA%Keir.Fraser@cl.cam.ac.uk>
2007-12-06 14:53 ` Christoph Egger
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=200711291402.14214.Christoph.Egger@amd.com \
--to=christoph.egger@amd.com \
--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 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.