From mboxrd@z Thu Jan  1 00:00:00 1970
From: Anthony Liguori <aliguori@us.ibm.com>
Subject: [PATCH 0/2] Change xs_read_watch interfaces to support
	variable arguments
Date: Mon, 03 Oct 2005 23:43:43 -0500
Message-ID: <4342087F.5010505@us.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Christian Limpach <Christian.Limpach@cl.cam.ac.uk>, Rusty Russell <rusty@rustcorp.com.au>, xen-devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

The following set of changes modify the read_watch interface in 
userspace and in the kernel to support variable arguments.  This is in 
preparation for adding domid to @{introduce,release}Domain watches.  
This will allow backends to automatically reap on domain destruction 
which should eliminate a large number of the zombie problems we're 
having on domain destruction since Xend no longer plays a role in 
freeing that memory.

The interface for read_watch is now consistent between userspace and 
kernel space.  It's modelled after xs_read_directory.  The returned 
array is indexable via XS_WATCH_* macros.

While slightly awkward, IMHO it seems like the cleanest and most 
flexible option of the proposed interfaces.

Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>

Regards,

Anthony Liguori