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

[Xen-devel] copy_to_user in another domain?

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] copy_to_user in another domain?
From: "Bryan D. Payne" <bryan@xxxxxxxxxxxx>
Date: Thu, 20 Apr 2006 09:11:21 -0400
Delivery-date: Thu, 20 Apr 2006 06:11:48 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I've got the following scenario... I'm handling a hypercall from domain A and would like to copy some data from the hypervisor to domain B. From what I can tell, it looks like the copy_to_user function (and all of its related functions) will only copy data back into domain A for me. I've been combing the hypervisor code and can't seem to find a good way to copy the data into domain B. Is there a built-in function for this? Or would I need to do something more like delay the copy until domain B is scheduled or ??

Thanks,
bryan


-
Bryan D. Payne
Graduate Student, Computer Science
Georgia Tech Information Security Center
http://www.bryanpayne.org



Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>