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>
Subject: Re: [Xen-ia64-devel] [PATCH][RFC][TAKE4] the P2M/VP patches
From: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
Date: Wed, 12 Apr 2006 15:09:49 +0900
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx, Tristan Gingold <Tristan.Gingold@xxxxxxxx>
Delivery-date: Tue, 11 Apr 2006 23:10:01 -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: Mutt/1.4.2.1i
On Wed, Apr 12, 2006 at 01:16:37PM +0800, Tian, Kevin wrote:
> >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.

Hi Kevin. Thanks for your testing.
The Tristan's log said that no page is assigned to the 0xfae0000 area.
It doesn't seem that MMIO area covers the 0xfae0000 area.
So Tristan's case is different from Alex's.
MDT table must be confirmed.

For Alex's case dom_fw_init() must be modified so that
dom_fw_dom0_pasthrough() is called at first and then
conventional memory should be mapped without overlap.



>       In my test, domU can boot however with two stack dumps.
> One for 0xfee0000, and another for 0xffffc019064 (0x60). Previous
> one is related to IPI which will disappear when guest SMP is ready.
> The later one shouldn't be there since domU shouldn't have access
> to legacy I/O in current model (Later may change for driver domain). That's 
> an access to keyboard port possibly because now xen0/xenU
> is compiled as one image with more drivers added. Maybe it's better
> for us to map all 64M mmio area of domU to a dummy page at current
> stage, to remove warnings and walk around some native drivers
> within domU. Later when driver domain is added, we can map specific
> mmio page to machine mmio range per configuration.

I agree with you.
But this issues isn't specific to the P2M/VP patch.
Linux VGA driver doesn't take care of the mmio base address.
So it should be also modified or disabled.
-- 
yamahata

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

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