From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel De Graaf Subject: Re: [PATCH v6 0/3] libxenvchan: interdomain communications library Date: Fri, 30 Sep 2011 10:40:11 -0400 Message-ID: <4E85D4CB.80009@tycho.nsa.gov> References: <1313764724-12683-1-git-send-email-dgdegra@tycho.nsa.gov> <1316729665-15004-1-git-send-email-dgdegra@tycho.nsa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Vasiliy Tolstov Cc: Ian.Campbell@eu.citrix.com, xen-devel@lists.xensource.com, Ian.Jackson@eu.citrix.com, konrad.wilk@oracle.com, Stefano.Stabellini@eu.citrix.com List-Id: xen-devel@lists.xenproject.org On 09/30/2011 04:28 AM, Vasiliy Tolstov wrote: > 2011/9/30 Vasiliy Tolstov > >> >> >> 2011/9/23 Daniel De Graaf >> >>> Changes since v5: >>> - Unify gntdev osdep interface >>> - Eliminate notify_result and revert mapping if notify ioctl fails >>> - Rename functions and structures to libxenvchan >>> - Use application-specified xenstore path for ring/event data >>> - Enforce maximum ring size of 2^20 bytes on client >>> - Change to LGPL 2.1 >>> >>> [PATCH 1/3] libxc: add xc_gnttab_map_grant_ref_notify >>> [PATCH 2/3] libxc: add xc_gntshr_* functions >>> [PATCH 3/3] libvchan: interdomain communications library >>> >>> >>> >> Hello. Sorry for bumping.. >> What version of xen kernel i need to use this library? Now i have 2.6.32.26 >> in many domUs. >> And what i need in dom0 for that, if i want to communicate via libxenvchan >> from domU to dom0? >> >> >> > And where i can find latest version of the patch? > This library depends on gntdev for the client and gntalloc for the server; these were merged in 2.6.39. The client can be used with 2.6.32.x kernels however it is not possible to detect when a peer crashes or exits without calling libxenvchan_close() on that kernel. This library does not require that either peer is dom0; it can be used for both domU-domU and domU-dom0 communication. The latest version of the patch can be found in the xen-devel archives. -- Daniel De Graaf National Security Agency