Re: [Xen-devel] [PATCH v3 2/4] docs: Document a xenstore path for PV driver version information...

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Paul Durrant writes ("[Xen-devel] [PATCH v3 2/4] docs: Document a xenstore path 
for PV driver version information..."):
> diff --git a/docs/misc/xenstore-paths.markdown 
> b/docs/misc/xenstore-paths.markdown
> index 71dfda2..cae5115 100644
> --- a/docs/misc/xenstore-paths.markdown
> +++ b/docs/misc/xenstore-paths.markdown
> @@ -37,6 +37,8 @@ before regexp expansion:
>    the "other" domain. i.e. ~ refers to the domain providing a service
>    while $DOMID is the consumer of that service.
>  * $UUID -- a UUID in the form xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
> +* $NAME -- a string identifying an object within a domain. Typically
> +  comprising only alphanumeric characters.
...
> +* VERSION -- 1, 2 or 3 integers, in decimal form separated by "."
> +             followed by a STRING suffix (starting with the first
> +             non-numeric character).
> +             The integers are a version number of the form MAJOR,
> +             MAJOR.MINOR or MAJOR.MINOR.MICRO respectively.

This string is not really useful or useable in this form.  Who assigns
these version numbers ?  Maybe we need Vendor / Product / Version or
something (a la SCSI or something).

Also we need some explanation of what this is for.

In particular, is it part of protocol negotiation or bug workaround ?
Given the format, hopefully not.  In which case that needs to be
explicitly stated.

If it is to be used for bug workaround, it definitely needs to be more
structured.

Thanks,
Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel