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

[XenPPC] Re: [Xen-devel] [PATCH] xencomm, xenmem and hypercall continuation



On 10/11/06 10:42, "Isaku Yamahata" <yamahata@xxxxxxxxxxxxx> wrote:

>> This is the best option I think. But I'm loathe to make it part of the
>> guest_handle API. We should avoid getting into this mess in the first place
>> for future hypercalls, so this will be a memory-specific function.
>> 
>> We should stick it at the top of memory.c, with a comment and make it a
>> no-op dependent on something like ARCH_HAS_XENCOMM (or just __ia64__ ||
>> __powerpc__ would be fine, actually, since it's just one place).
> 
> Here is the patch. Powerpc guys may have their own idea, though.
> Unfortunately 4 #ifndef's are needed.

That's still pretty bad. I'll rewrite the hypercall to avoid using
guest_handle_add_offset().

 -- Keir


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


 


Rackspace

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