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] Handling Xen ioctls in Valgrind

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Handling Xen ioctls in Valgrind
From: Tim Post <echo@xxxxxxxxxxxx>
Date: Sat, 06 Jun 2009 11:15:22 +0800
Delivery-date: Fri, 05 Jun 2009 20:15:58 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Reply-to: echo@xxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

I am about to upload a patch to Valgrind which will allow it to handle
Xen privcmds.

To do this, I have to basically copy the contents of Linux/privcmd.h
into the Valgrind tree and re-namespaceize it (i.e. privcmd_hypercall
would become VKI_privcmd_hypercall). 

Is there any chance of privcmd_hypercall_t, privcmd_mmap_entry_t,
privcmd_mmap_t, privcmd_mmapbatch_t or their dependencies changing? If
so, I'll just maintain a patch to add them that interested people can
use and not submit them upstream yet.

Thanks in advance
--Tim


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

<Prev in Thread] Current Thread [Next in Thread>