Displaying 5 results from an estimated 5 matches for "libxl_noblktap2".
Did you mean:
libxl_blktap2
2012 Nov 07
4
[PATCH 1/2] 4.1.2 blktap2 cleanup fixes.
...tapdisk process associated with the backend represented
+ * by be_path.
+ */
+_hidden void libxl__device_destroy_tapdisk(libxl__gc *gc, char *be_path);
+
_hidden char *libxl__uuid2string(libxl__gc *gc, const libxl_uuid uuid);
struct libxl__xen_console_reader {
diff -r 700d0f03d50a tools/libxl/libxl_noblktap2.c
--- a/tools/libxl/libxl_noblktap2.c Mon Oct 29 09:04:48 2012 +0100
+++ b/tools/libxl/libxl_noblktap2.c Tue Nov 06 19:52:48 2012 -0600
@@ -27,3 +27,7 @@ const char *libxl__blktap_devpath(libxl_
{
return NULL;
}
+
+void libxl__device_destroy_tapdisk(libxl__gc *gc, char *be_path)
+{
+}
------...
2011 Sep 21
1
[PATCH] libxl: attempt to cleanup tapdisk processes on disk backend destroy
...associated with the backend represented
+ * by be_path.
+ */
+_hidden void libxl__device_destroy_tapdisk(libxl__gc *gc, char *be_path);
+
_hidden char *libxl__uuid2string(libxl__gc *gc, const libxl_uuid uuid);
struct libxl__xen_console_reader {
diff -r 206afa070919 -r b43fd821d1ae tools/libxl/libxl_noblktap2.c
--- a/tools/libxl/libxl_noblktap2.c Wed Sep 21 13:59:24 2011 +0100
+++ b/tools/libxl/libxl_noblktap2.c Wed Sep 21 13:59:24 2011 +0100
@@ -27,3 +27,7 @@ char *libxl__blktap_devpath(libxl__gc *g
{
return NULL;
}
+
+void libxl__device_destroy_tapdisk(libxl__gc *gc, char *be_path)
+{
+}
_____...
2013 Oct 21
36
[PATCH 0 of 5 V3] Remus/Libxl: Network buffering support
This patch series adds support for network buffering in the Remus
codebase in libxl.
Changes in V3:
[1/5] Fix redundant checks in configure scripts
(based on Ian Campbell''s suggestions)
[2/5] Introduce locking in the script, during IFB setup.
Add xenstore paths used by netbuf scripts
to xenstore-paths.markdown
[3/5] Hotplug scripts setup/teardown invocations are now
2013 Nov 01
17
[PATCH v2 00/14] xen: arm: 64-bit guest support and domU FDT autogeneration
I''ve addressed all (I think/hope) of the review comments.
The main change is to expose the guest virtual platform (e.g. memory
layout and interrupt usage etc) to the toolstack via the public
interface. This is then used during FDT generation. I have just codified
the current defacto standard layout, it''s probably not the best layout
but any change can be a separate patch/series.
2013 Nov 19
23
[PATCH v6 00/16] xen: arm: 64-bit guest support and domU FDT autogeneration
Biggest change is to switch the new DTB node to /xen-core-devices
instead of /xen at Stefano''s request.
I also dropped the few patches title HACK etc which weren''t supposed to
be there and fixed up some bits and pieces which folks commented on.
George, WRT the freeze I think this is functionality which we cannot
ship Xen 4.4 without. The impact is entirely constrained to the