search for: write_req

...L) +#define xenbus_unwatch_path(xbt, path) xenbus_unwatch_path_token(xbt, path, XENBUS_WATCH_PATH_TOKEN) + /* Associates a value with a path. Returns a malloc''d error string on failure. */ char *xenbus_write(xenbus_transaction_t xbt, const char *path, const char *value); + +struct write_req { + const void *data; + unsigned len; +}; + +/* Send a message to xenbus, in the same fashion as xb_write, and + block waiting for a reply. The reply is malloced and should be + freed by the caller. */ +struct xsd_sockmsg * +xenbus_msg_reply(int type, + xenbus_transaction...

...; NR_REQS) @@ -95,6 +98,7 @@ static int allocate_xenbus_id(void) } o_probe = probe; + for (;;) { if (!req_info[o_probe].In_Use) @@ -179,11 +183,11 @@ static void xb_write(int type, int req_i { XENSTORE_RING_IDX prod; int r; - int len = 0; + size_t len = 0; const struct write_req *cur_req; - int req_off; - int total_off; - int this_chunk; + size_t req_off; + size_t total_off; + size_t this_chunk; struct xsd_sockmsg m = {type, req_id, trans_id }; struct write_req header_req = { &m, sizeof(m) }; @@ -347,16 +351,15 @@ char* xenbus_wait_for_value(const char* /...

This patch series contains a set of patches making minios rather easier to use, from an application development point of view. Overview of patches: 1 Command line argument parsing support, from Xen. 2 Weak console handler function. 3 Build system tweaks for application directories. 4 Trailing whitespace cleanup. (because it is very messy) Patch 4 is likely to be more controversial than