[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#11460


  • To: "Isaku Yamahata" <yamahata@xxxxxxxxxxxxx>
  • From: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
  • Date: Fri, 22 Sep 2006 17:11:33 +0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 22 Sep 2006 02:13:46 -0700
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcbeJr5PdGwitAT/RXGG9FrRdE6QCQAAEOgw
  • Thread-topic: [Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#11460


>-----Original Message-----
>From: Isaku Yamahata [mailto:yamahata@xxxxxxxxxxxxx]
>Sent: 2006年9月22日 17:09
>To: Xu, Anthony
>Cc: You, Yongkang; xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>Subject: Re: [Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#11460
>
>
>On Fri, Sep 22, 2006 at 01:50:34PM +0800, Xu, Anthony wrote:
>> 1) 2 cases failed because "can not allocate memory" issue.
>>
>> This may be caused by failure of hypercall.
>> Hypercal fails because this hypercall use pointer to pass parameter.
>> But in XEN/IA64, copy_from/to_user don't guarantee to work.
>> This is a big potential issue on XEN/IA64.
>> In XEN/PPC, seems they use guest physical pointer to resolve this issue.
>>
>> What's your opinion about this?
>
>I think xencomm is the way to go.
>If Tristan ceases pushing it,
>we, VA Linux, are willing to take over it.
>--
>yamahata

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.