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: "Isaku Yamahata" <yamahata@xxxxxxxxxxxxx>, "Tristan Gingold" <Tristan.Gingold@xxxxxxxx>
Subject: RE: [Xen-ia64-devel] [PATCH][RFC][TAKE4] the P2M/VP patches
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Wed, 12 Apr 2006 13:16:37 +0800
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 11 Apr 2006 22:16:58 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcZdSa8MGqmC4zN6R1es/epUbyLNxQAo6qXg
Thread-topic: [Xen-ia64-devel] [PATCH][RFC][TAKE4] the P2M/VP patches
>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.

        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.

Thanks,
Kevin
>
>
>diff -r e2003842daeb xen/arch/ia64/xen/domain.c
>--- a/xen/arch/ia64/xen/domain.c        Mon Apr 10 15:08:03 2006
>+0900
>+++ b/xen/arch/ia64/xen/domain.c        Tue Apr 11 18:21:34 2006
>+0900
>@@ -752,6 +752,7 @@ assign_domain_mmio_page(struct domain *d
>     if (size == 0) {
>         printk("%s: domain %p mpaddr 0x%lx size = 0x%lx\n",
>                __func__, d, mpaddr, size);
>+        size = PAGE_SIZE;
>     }
>     assign_domain_same_page(d, mpaddr, size);
>     return mpaddr;
>
>
>--
>yamahata
>
>_______________________________________________
>Xen-ia64-devel mailing list
>Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-ia64-devel

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

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