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-ppc-devel

[XenPPC] [PATCH] [UPDATE] Xencomm

To: xen-ppc-devel <xen-ppc-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [XenPPC] [PATCH] [UPDATE] Xencomm
From: Jerone Young <jyoung5@xxxxxxxxxx>
Date: Mon, 29 Jan 2007 00:45:08 -0600
Delivery-date: Sun, 28 Jan 2007 22:44:47 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ppc-devel-request@lists.xensource.com?subject=help>
List-id: Xen PPC development <xen-ppc-devel.lists.xensource.com>
List-post: <mailto:xen-ppc-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: IBM
Reply-to: jyoung5@xxxxxxxxxx
Sender: xen-ppc-devel-bounces@xxxxxxxxxxxxxxxxxxx
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
<Prev in Thread] Current Thread [Next in Thread>