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

[XenPPC] [PATCH] [UPDATE] Xencomm



Here is yet another go at this. This patch I have thoroughly gone
thought. 

Changes:
        - move xencomm_map_early to xencomm_map_no_alloc

        - added xencomm_free everywhere
        
        - return ERRNOs instead of -1
         

Testing:
        - loaded Dom0
                - load modules xenblk(VIO) & xennet
        - lodaded DomU loading VI
                - load modules xenblk(VIO) & xennet
        
It appears that it allways hits create_inline everytime within the _map
functions and so xencomm_create_mini() & xencomm_create are not getting
worked out yet. 

But I think I've found problems making all the suggestions workout:

For xencomm_map & xencomm_map_no_alloc there is a bit of an issue. The
caller has to accept the fact that it will get physcial address, since
it does not know if argument address can be made inline or not. It has
to use the resulting address in the following hypercall, and converting
it is unsure, since if are argument address can be made to an inline you
are converting a physical address to an invalid physical address. 

The other problem that is created in this case is where we get an
physical address from xencomm_map that is returned from function
xencomm_pa() and cannot be simply converted back to a it's resulting
virtual address with __va().

If I'm wrong about this please blast away :-)

Signed-off-by: Jerone Young <jyoung5@xxxxxxxxxx>

Attachment: xencomm.patch
Description: Text Data

_______________________________________________
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®.