WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 785] Dom0 domains cannot be larger than 2GiB

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 785] Dom0 domains cannot be larger than 2GiB
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Sat, 30 Sep 2006 07:17:57 -0700
Delivery-date: Sat, 30 Sep 2006 07:18:51 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <bug-785-3@xxxxxxxxxxxxxxxxxxxxxxxxxxx/bugzilla/>
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=785





------- Comment #1 from jimix@xxxxxxxxxxxxxx  2006-09-30 07:17 -------
The problem turns out to be that Dom0 tries to map the "IO-area" as regular
memory, the H_ENTER fails and its to early for Linux to recover.

On 970s the IO-Area starts at 2G and ends at 4G so a domain that has access to
the IO Area cannot have memory in that Domain Physical address.

Since the Devtree has several carefully placed references into the IO-area it
is not feasible to place the IO-Area in a different physical space of the
domain because it would require translating the devtree as well.


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs

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