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

RE: [Xen-devel] [PATCH 8/9] tmem: invocations of tmemcodefromexisting xe

To: Jan Beulich <jbeulich@xxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH 8/9] tmem: invocations of tmemcodefromexisting xen code
From: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Date: Mon, 9 Feb 2009 21:26:11 +0000 (GMT)
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 09 Feb 2009 13:27:33 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <49900414.76E4.0078.0@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> If it seems to cumbersome, just leave it off for the moment, 
> and I'll submit
> a fixup patch after it got merged.

Thanks very much!  I'll leave my partially complete compat
changes in the next round as there are probably just one
or two things I am missing.
 
> But you ought to be using
> guest_handle_cast there (and perhaps elsewhere) anyway (rather than
> referencing handle.p directly), which would allow hiding any 
> masking in
> case it would turn out necessary.

I think cli_mfn_to_va() is the only place.  Since the current
code works and my attempts to fix it to use guest_handle_cast
have failed, I'd appreciate post-merge fixup help here too!

Thanks,
Dan

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