This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] [timer/ticks related] dom0 hang during boot on large 1TB

To: "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx>, <mukesh.rathor@xxxxxxxxxx>
Subject: RE: [Xen-devel] [timer/ticks related] dom0 hang during boot on large 1TB system
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Tue, 22 Dec 2009 17:02:53 +0000
Cc: kurt.hackel@xxxxxxxxxx, Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Xen-devel@xxxxxxxxxxxxxxxxxxx, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Tue, 22 Dec 2009 09:03:15 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <526a5845-c007-4740-b0a2-f6f1cf372a08@default>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4B30F5A2020000780002736B@xxxxxxxxxxxxxxxxxx> <526a5845-c007-4740-b0a2-f6f1cf372a08@default>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> Dan Magenheimer <dan.magenheimer@xxxxxxxxxx> 22.12.09 17:05 >>>
>> From: Jan Beulich [mailto:JBeulich@xxxxxxxxxx] 
>> >>> Dan Magenheimer <dan.magenheimer@xxxxxxxxxx> 22.12.09 16:30 >>>
>> >Mukesh's work has been on a 32-bit dom0.
>> Which seems quite odd a combination - 1Tb of memory, but a 32-bit
>> Dom0 -, which is why initially I didn't even consider the 
>> possibility. I'm
>> afraid you're asking for more trouble with this.
>Indeed.  Oracle expects to move to a 64-bit dom0 in a "future"
>release, but we have to make the 32-bit dom0 work until then.
>Our default configuration specifies dom0_mem=xxx which I would
>assume would eliminate most or all of the "trouble" you are
>referring to, but, Mukesh, could you confirm what dom0_mem
>is set to?

No, that won't help. I'm referring to things like Dom0 accesses to the
M2P table it sees, which doesn't cover even nearly all memory. I can't
say whether that can go without problem, but without closely looking
at it I don't think you can assume this would work. Likewise I would
suspect tools issues (if you use the tools from xen-unstable et al),
though I have no precise pointer right now at specific issues.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>