On 08/05/17 12:13, Ian Jackson wrote:
> Juergen Gross writes ("[PATCH 3/3] docs: document CONTROL command of xenstore
> protocol"):
>> The CONTROL command (former DEBUG command) isn't specified in the
>> xenstore protocol doc. Add it.
> ...
>> -DEBUG print|<string>|?? sends <string> to
>> debug log
>> -DEBUG print|<thing-with-no-nul> EINVAL
>> -DEBUG check|?? checks xenstored
>> innards
>> -DEBUG <anything-else|> no-op (future
>> extension)
>> +CONTROL <command>|[<parameters>|]
>> + Send a control command <command> with optional parameters
>> + (<parameters>) to Xenstore daemon. <command> support is
>> + implementation specific and might change in future.
>>
>> - These requests should not generally be used and may be
>> - withdrawn in the future.
>
> I should retain a stronger imprecation. How about:
>
> The set of commands and their semantics is implementation
> specific and is likely to change from one Xen version to the
> next. Out-of-tree users will encounter compatibility issues.
I'm fine with this.
Juergen
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xen.org/xen-devel
