All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Paul Durrant <paul.durrant@citrix.com>, xen-devel@lists.xenproject.org
Cc: Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
	Keir Fraser <keir@xen.org>,
	Ian Campbell <ian.campbell@citrix.com>,
	Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH 2/4] docs: Document a xenstore path for PV driver version information...
Date: Fri, 6 Nov 2015 18:05:21 +0000	[thread overview]
Message-ID: <563CEBE1.6030609@citrix.com> (raw)
In-Reply-To: <1446830507-4233-4-git-send-email-paul.durrant@citrix.com>

On 06/11/15 17:21, Paul Durrant wrote:
> ...to be advertised by a guest.
>
> For domain management purposes it is convenient to be able to see
> PV driver version information in xenstore. The XAPI toolstack in
> XenServer has always created a ~/drivers path for this purpose.
>
> This patch documents that path and also adds a specification of how
> it should be used.
>
> Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
> Cc: Ian Campbell <ian.campbell@citrix.com>
> Cc: Ian Jackson <ian.jackson@eu.citrix.com>
> Cc: Jan Beulich <jbeulich@suse.com>
> Cc: Keir Fraser <keir@xen.org>
> Cc: Tim Deegan <tim@xen.org>
> ---
>  docs/misc/xenstore-paths.markdown | 10 ++++++++++
>  1 file changed, 10 insertions(+)
>
> diff --git a/docs/misc/xenstore-paths.markdown b/docs/misc/xenstore-paths.markdown
> index ec3cc5f..7701632 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.
>  
>  VALUES are strings and can take the following forms:
>  
> @@ -51,6 +53,9 @@ VALUES are strings and can take the following forms:
>  * (VALUE | VALUE | ... ) -- a set of alternatives. Alternatives are
>    separated by a "|" and all the alternatives are enclosed in "(" and
>    ")".
> +* VERSION -- 2 or 3 integers, in decimal form separated by ".",
> +             specifying major version, minor version, and then
> +	     (optionally) micro version.

I am not sure version should come with a restriction like this.  For
debug builds, it might be common to have a suffix.  Furthermore, not all
software conforms to the $MAJOR.$MINOR.$MICRO scheme.

I would just leave it specified as a "string which identifies the
version of the driver", without any specific restrictions

~Andrew

  reply	other threads:[~2015-11-06 18:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06 17:21 [PATCH 0/4] docs: Document xenstore paths Paul Durrant
2015-11-06 17:21 ` [PATCH 1/4] docs: Document control features the can be advertised by guests Paul Durrant
2015-11-09 10:44   ` Jan Beulich
2015-11-09 11:01     ` Paul Durrant
2015-11-06 17:21 ` [PATCH 2/4] docs: Document a path for PV driver version information Paul Durrant
2015-11-06 17:25   ` Paul Durrant
2015-11-06 17:21 ` [PATCH 2/4] docs: Document a xenstore " Paul Durrant
2015-11-06 18:05   ` Andrew Cooper [this message]
2015-11-06 17:21 ` [PATCH 3/4] docs: Document xenstore paths for domain hotplug features Paul Durrant
2015-11-06 18:08   ` Andrew Cooper
2015-11-09  9:51     ` Paul Durrant
2015-11-09 10:50       ` Jan Beulich
2015-11-09 11:01         ` Paul Durrant
2015-11-06 17:21 ` [PATCH 4/4] docs: Document xenstore paths for domain network address information Paul Durrant
2015-11-06 18:16   ` Andrew Cooper
2015-11-09  9:55     ` Paul Durrant

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=563CEBE1.6030609@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=keir@xen.org \
    --cc=paul.durrant@citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.