Xen devel - Jun 2009 - Handling Xen ioctls in Valgrind

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@lists.xensource.com
http://lists.xensource.com/xen-devel

On 06/06/2009 04:15, "Tim Post" <echo@echoreply.us> wrote:
> 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.
We may add more ioctls in future, but the old set will continue to be
supported for compatibility.

 -- Keir



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