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-ia64-devel

Re: [Xen-ia64-devel] [PATCH][RFC][TAKE4] the P2M/VP patches

To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, "Isaku Yamahata" <yamahata@xxxxxxxxxxxxx>
Subject: Re: [Xen-ia64-devel] [PATCH][RFC][TAKE4] the P2M/VP patches
From: Tristan Gingold <Tristan.Gingold@xxxxxxxx>
Date: Wed, 12 Apr 2006 08:02:52 +0100
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 11 Apr 2006 23:59:04 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <571ACEFD467F7749BC50E0A98C17CDD8094E7AF6@pdsmsx403>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <571ACEFD467F7749BC50E0A98C17CDD8094E7AF6@pdsmsx403>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.5
Le Mercredi 12 Avril 2006 07:16, Tian, Kevin a écrit :
> From: Isaku Yamahata
>
> >Sent: 2006年4月11日 17:23
> >
> >It seems that the IOSAPIC area is not mapped to dom0.
> >Does the following patch make difference?
> >Could you send the all log?
>
> Hi, Isaku,
>       If the 0xfae0000 is the address of one IOSAPIC area, why
> doesn't it get mapped at dom_fw_init? From your patch,
> dom_fw_dom0_passthrough should already construct mapping for entries
> exported to dom0. So instead the problematic point
> may be like Alex's case, where the type of 0xfae0000 area is a
> new one out of the comparison in current code. Maybe Tristan
> can confirm this point.
No.  0xfae00000 is simply not in the memmap!
I don't know why, I am asking to BIOS people.
If I have a few minutes, I could try to patch the memmap to extend an entry.

Tristan.


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

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