RE: [Xen-ia64-devel] [PATCH] Add event callback for xen/ia64

["Tian, Kevin" <kevin.tian@xxxxxxxxx>]

Seems I didn't observe the final result before sending out last mail.
 Actually domU still boots even with stack content dumped there, 
and I finally login to level 3. However because bridge is not setup 
yet, so eth0 doesn't up.

Thanks,
Kevin

>-----Original Message-----
>From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
>Tian, Kevin
>Sent: 2006年4月12日 12:01
>To: Alex Williamson
>Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx; Tristan Gingold
>Subject: RE: [Xen-ia64-devel] [PATCH] Add event callback for xen/ia64
>
>>From: Alex Williamson [mailto:alex.williamson@xxxxxx]
>>Sent: 2006年4月12日 11:30
>>
>>On Wed, 2006-04-12 at 11:22 +0800, Tian, Kevin wrote:
>>> 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?
>>
>>   I'm using Isaku's patch set plus the patch I sent in the same thread
>>that makes it work on zx1 systems.  That patch may or may not help
>>you.
>
>I'll give it a try.
>
>>One important thing that I think it does is sort the MDT created for
>>dom0.  I also had to add EFI_ACPI_RECLAIM_MEMORY to the MDT
>>entry types
>>that get added for dom0.  For me this included the area where the
>ACPI
>>tables live.  You may want to look at your MDT and see if there's
>>another type you can add that will cover 0xfee00000.  BTW, the 8250
>
>OK
>
>>serial driver is disabled with the config files provided in Isaku's
>>patches, so the serial console is only good for output with them.
>>Thanks,
>
>See it now. So that's not issue.
>
>BTW, when you observed domU network degradation, how about
>the network of dom0? If dom0 is not affected, it's obvious that the
>whole event path is placed lower priority than whole interrupt path,
>and thus affects virtual drivers. If that's the case, I'll check whether
>some logic can be added to match original flow.
>
>Thanks,
>Kevin
>
>_______________________________________________
>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