Sander Eikelenboom writes ("Re: [Xen-devel] Xenstore watch interface in the
kernel"):
> Something I did ran into while trying to use xenstore, was that the
> callbacks don't give back the previous and current value.
Others have replied to this, and I agree with them, but: th
On 22/12/16 12:59, Juergen Gross wrote:
On 22/12/16 13:49, Sander Eikelenboom wrote:
Thursday, December 22, 2016, 1:22:06 PM, you wrote:
Juergen Gross writes ("Xenstore watch interface in the kernel"):
While working on the Linux xenbus kernel driver I stumbled over a rather
strange interface:
On 22/12/16 13:49, Sander Eikelenboom wrote:
>
> Thursday, December 22, 2016, 1:22:06 PM, you wrote:
>
>> Juergen Gross writes ("Xenstore watch interface in the kernel"):
>>> While working on the Linux xenbus kernel driver I stumbled over a rather
>>> strange interface: a Xenstore watch event is
Thursday, December 22, 2016, 1:22:06 PM, you wrote:
> Juergen Gross writes ("Xenstore watch interface in the kernel"):
>> While working on the Linux xenbus kernel driver I stumbled over a rather
>> strange interface: a Xenstore watch event is delivered via a callback
>> defined as:
>>
>> void (*
Juergen Gross writes ("Xenstore watch interface in the kernel"):
> While working on the Linux xenbus kernel driver I stumbled over a rather
> strange interface: a Xenstore watch event is delivered via a callback
> defined as:
>
> void (*callback)(struct xenbus_watch *,
> c
While working on the Linux xenbus kernel driver I stumbled over a rather
strange interface: a Xenstore watch event is delivered via a callback
defined as:
void (*callback)(struct xenbus_watch *,
const char **vec, unsigned int len);
vec is an array of strings and len the n
