|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v4 11/34] xsplice: Design document
>>> On 24.03.16 at 04:15, <konrad.wilk@xxxxxxxxxx> wrote:
> +### XEN_SYSCTL_XSPLICE_LIST (2)
> +
> +Retrieve an array of abbreviated status and names of payloads that are
> loaded in the
> +hypervisor.
> +
> +The caller provides:
> +
> + * `version`. Version of the payload. Caller should re-use the field
> provided by
> + the hypervisor. If the value differs the data is stale.
> + * `idx` index iterator. The index into the hypervisor's payload count. It is
> + recommended that on first invocation zero be used so that `nr` (which the
> + hypervisor will update with the remaining payload count) be provided.
> + Also the hypervisor will provide `version` with the most current value.
This reads okay now.
> +struct xen_sysctl_xsplice_list {
> + uint32_t version; /* OUT: Hypervisor stamps value.
> + If varies between calls, we
> are
> + getting stale data. */
> + uint32_t idx; /* IN: Index into array. */
But the comment here can really only be taken to refer to one or
more of the arrays the following handles point at.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |