xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Daniel De Graaf <dgdegra@tycho.nsa.gov>
Cc: jbeulich@suse.com, ian.campbell@citrix.com, msw@amazon.com,
	xen-devel@lists.xen.org
Subject: Re: [PATCH v2] xen/sysfs: Use XENVER_guest_handle to query UUID
Date: Wed, 22 Aug 2012 12:57:53 -0400	[thread overview]
Message-ID: <20120822165753.GA3328@phenom.dumpdata.com> (raw)
In-Reply-To: <1345149626-32602-1-git-send-email-dgdegra@tycho.nsa.gov>

On Thu, Aug 16, 2012 at 04:40:26PM -0400, Daniel De Graaf wrote:
> On 08/16/2012 04:22 PM, Matt Wilson wrote:
> > 
> > Hi Daniel,
> > 
> > What do you think about retaining a fallback of looking in xenstore if
> > the hypercall fails?
> > 
> > Matt
> > 
> 
> That sounds good; there's little cost to leaving the fallback in.

applied
> 
> ----8<-----------------------------------------------------
> 
> This hypercall has been present since Xen 3.1, and is the preferred
> method for a domain to obtain its UUID. Fall back to the xenstore method
> if using an older version of Xen (which returns -ENOSYS).
> 
> Signed-off-by: Daniel De Graaf <dgdegra@tycho.nsa.gov>
> ---
>  drivers/xen/sys-hypervisor.c    | 13 ++++++++++++-
>  include/xen/interface/version.h |  3 +++
>  2 files changed, 15 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/xen/sys-hypervisor.c b/drivers/xen/sys-hypervisor.c
> index 4c7db7d..284df8a 100644
> --- a/drivers/xen/sys-hypervisor.c
> +++ b/drivers/xen/sys-hypervisor.c
> @@ -114,7 +114,7 @@ static void xen_sysfs_version_destroy(void)
>  
>  /* UUID */
>  
> -static ssize_t uuid_show(struct hyp_sysfs_attr *attr, char *buffer)
> +static ssize_t uuid_show_fallback(struct hyp_sysfs_attr *attr, char *buffer)
>  {
>  	char *vm, *val;
>  	int ret;
> @@ -135,6 +135,17 @@ static ssize_t uuid_show(struct hyp_sysfs_attr *attr, char *buffer)
>  	return ret;
>  }
>  
> +static ssize_t uuid_show(struct hyp_sysfs_attr *attr, char *buffer)
> +{
> +	xen_domain_handle_t uuid;
> +	int ret;
> +	ret = HYPERVISOR_xen_version(XENVER_guest_handle, uuid);
> +	if (ret)
> +		return uuid_show_fallback(attr, buffer);
> +	ret = sprintf(buffer, "%pU\n", uuid);
> +	return ret;
> +}
> +
>  HYPERVISOR_ATTR_RO(uuid);
>  
>  static int __init xen_sysfs_uuid_init(void)
> diff --git a/include/xen/interface/version.h b/include/xen/interface/version.h
> index e8b6519..dd58cf5 100644
> --- a/include/xen/interface/version.h
> +++ b/include/xen/interface/version.h
> @@ -60,4 +60,7 @@ struct xen_feature_info {
>  /* arg == NULL; returns host memory page size. */
>  #define XENVER_pagesize 7
>  
> +/* arg == xen_domain_handle_t. */
> +#define XENVER_guest_handle 8
> +
>  #endif /* __XEN_PUBLIC_VERSION_H__ */
> -- 
> 1.7.11.2

      parent reply	other threads:[~2012-08-22 16:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-16 18:25 [PATCH RFC] xen/sysfs: Use XENVER_guest_handle to query UUID Daniel De Graaf
2012-08-16 20:22 ` Matt Wilson
2012-08-16 20:40   ` [PATCH v2] " Daniel De Graaf
2012-08-17  7:51     ` Ian Campbell
2012-08-17  9:36       ` Pasi Kärkkäinen
2012-08-17  9:39         ` Pasi Kärkkäinen
2012-08-22 16:57     ` Konrad Rzeszutek Wilk [this message]

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=20120822165753.GA3328@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=dgdegra@tycho.nsa.gov \
    --cc=ian.campbell@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=msw@amazon.com \
    --cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).