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] Add event callback for xen/ia64

To: "Alex Williamson" <alex.williamson@xxxxxx>
Subject: RE: [Xen-ia64-devel] [PATCH] Add event callback for xen/ia64
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Wed, 12 Apr 2006 11:22:31 +0800
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx, Tristan Gingold <Tristan.Gingold@xxxxxxxx>
Delivery-date: Tue, 11 Apr 2006 20:22:51 -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: AcZd32atnAAWv4PlRB2MeyQONKYRfQAACWJw
Thread-topic: [Xen-ia64-devel] [PATCH] Add event callback for xen/ia64
Bad news is that p2m patch doesn't work for me yet.

Dom0: keyboard doesn't work with "INIT: Id "S1" respawning too fast: disabled 
for 5 minute" shown there. But network can work

DomU: After xend start and xm create, domU hangs at similar place reported by 
Tristan. Seems mmio is not mapped correctly in p2m table... 

Did I miss anything else aside from the patch sets by Isaku?

Thanks,
Kevin

(XEN) 
xen-event-channel using irq 233
(XEN) 
lookup_domain_mpa: bad mpa 0xfee00000 (> 0x20000000)
(XEN) lookup_domain_mpa: d 0xf00000000410e1b8 id 1 current 0xf0000000042f8000 
id 0
(XEN) 
(XEN) Call Trace:
(XEN)  [<f0000000040818d0>] show_stack+0x80/0x90
(XEN)                                 sp=f0000000042ffc00 bsp=f0000000042f8dc8
(XEN)  [<f0000000040487a0>] lookup_domain_mpa+0x180/0x200
(XEN)                                 sp=f0000000042ffdd0 bsp=f0000000042f8da0
(XEN)  [<f00000000405a060>] translate_domain_pte+0xe0/0x170
(XEN)                                 sp=f0000000042ffdd0 bsp=f0000000042f8d68
(XEN)  [<f0000000040624c0>] vcpu_itc_d+0xb0/0x1b0
(XEN)                                 sp=f0000000042ffdd0 bsp=f0000000042f8d28
(XEN)  [<f000000004057f80>] ia64_hyperprivop+0x190/0x600
(XEN)                                 sp=f0000000042ffde0 bsp=f0000000042f8cf8
(XEN)  [<f00000000405bbc0>] ia64_handle_break+0x150/0x280
(XEN)                                 sp=f0000000042ffe00 bsp=f0000000042f8cb8
(XEN)  [<f000000004080500>] ia64_leave_kernel+0x0/0x310
(XEN)                                 sp=f0000000042ffe00 bsp=f0000000042f8cb8
(XEN)  [<a000000100009090>] ???
(XEN)                                 sp=f000000004300000 bsp=f0000000042f8c98
(XEN)  [<a000000100053b40>] ???
(XEN)                                 sp=f0000000043

>From: Alex Williamson [mailto:alex.williamson@xxxxxx]
>Sent: 2006年4月12日 11:15
>
>On Wed, 2006-04-12 at 10:49 +0800, Tian, Kevin wrote:
>
>> OK, thanks for info. I'm currently building the tree and will test soon.
>> BTW, do you have any extra steps beside normal flow to setup the
>> network for domU?
>
>   For me it was simply commenting out the vif = [ '' ] line in my
>config file.  Then when I run xend start (it takes longer) and sets up a
>bridge and a few other network device.  domU boots up, sees an eth0
>device and it's configurable via dhcp.
>
>> Another side question I'm curious is, how about the bandwidth of
>> your physical NIC? Is 10M an acceptable data to you regarding
>> Isaku's p2m patch, which may reveal us the space for improvement
>> later? :-)
>
>   The testing I've done has not been 100% scientific.  I'm not on an
>isolated network and the server I'm pulling from is not dedicated for
>this testing.  I'm currently seeing ~95MB/s for the same test from dom0
>while domU is still getting ~10MB/s.  The bridge driver in dom0 is
>taking a some unaligned accesses, which may or may not be a
>significant
>factor for throughput.  It's possible I'm only seeing a few of them
>because of the printk rate limited in the unaligned code.  Thanks,
>
>       Alex
>
>--
>Alex Williamson                             HP Linux & Open
>Source Lab

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