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/
Home Products Support Community News


[Xen-devel] [PATCH 00/14] Logging cleanups, libxc API change

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [PATCH 00/14] Logging cleanups, libxc API change
From: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
Date: Thu, 27 May 2010 17:01:00 +0100
Cc: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
Delivery-date: Thu, 27 May 2010 09:20:52 -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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
In this patch series I do some serious cleanup.  In particular:
 * Remove all static global variables from libxc
   so that the library is fully reentrant.
 * Allow all callers of libxs, libxc, libxl to control
   where log messages to go.
 * Assorted other minor fixups.

This involves an incompatible change to the interface to libxc.
Instead of simply getting an int representing a file descriptor,
callers now get an xc_interface*.  Also, there are three new
parameters to xc_interface_open for which naive callers may pass 0.

The overall result is that (amongst other things) the stderr output
from "xl" is much more sensible.

(This is a resend of the series with the patches numbered in the
Subject line as they should have been.  Sorry for the inconvenience.)

Signed-off-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>

Xen-devel mailing list

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