All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: xen-devel@lists.xenproject.org,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH 6/8] libxl: allow a generation ID to be specified at domain creation
Date: Fri, 27 Jun 2014 12:16:02 +0100	[thread overview]
Message-ID: <1403867762.25894.30.camel@kazak.uk.xensource.com> (raw)
In-Reply-To: <1403107977-13795-7-git-send-email-david.vrabel@citrix.com>

On Wed, 2014-06-18 at 17:12 +0100, David Vrabel wrote:
> Toolstacks may specify a VM generation ID using the u.hvm.ms_vm_genid
> field in the libxl_domain_build_info structure, when creating a
> domain.
> 
> The toolstack is responsible for providing the correct generation ID
> according to the Microsoft specification (e.g., generating new random
> ones with libxl_ms_vm_genid_generate() as appropriate when restoring).
> 
> Although the specification requires that a ACPI Notify event is raised
> if the generation ID is changed, the generation ID is never changed
> when the domain is in a state to receive such an event (it's either
> newly created or suspended).
> 
> Signed-off-by: David Vrabel <david.vrabel@citrix.com>

Acked-by: Ian Campbell <ian.campbell@citrix.com>

And I intend to apply but one question:

> +bool libxl_ms_vm_genid_is_zero(const libxl_ms_vm_genid *id)
> +{
> +    static const libxl_ms_vm_genid zero;

Does this formally end up in .bss and is therefore definitely zero?

If it were global I'd have no doubt, but I'm not sure about it in this
scope.

Regardless, I'll assume for now that it is right. If not please send a
follow up with the necessary "= {0}".

Ian.

  reply	other threads:[~2014-06-27 11:16 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-18 16:12 [PATCHv6 0/8] tools: rework VM Generation ID David Vrabel
2014-06-18 16:12 ` [PATCH 1/8] libxc: add xc_hvm_param_get/set() to get/set 64-bit values David Vrabel
2014-06-18 16:12 ` [PATCH 2/8] libxl: add libxl__random_bytes() which fills a buffer with random bytes David Vrabel
2014-06-18 16:12 ` [PATCH 3/8] hvmloader: add helper functions to get/set HVM params David Vrabel
2014-06-18 16:12 ` [PATCH 4/8] hvm: add HVM_PARAM_VM_GENERATION_ID_ADDR David Vrabel
2014-06-18 16:12 ` [PATCH 5/8] libxc, libxl, hvmloader: strip out outdated VM generation ID implementation David Vrabel
2014-06-27 12:41   ` Ian Campbell
2014-06-18 16:12 ` [PATCH 6/8] libxl: allow a generation ID to be specified at domain creation David Vrabel
2014-06-27 11:16   ` Ian Campbell [this message]
2014-06-27 11:35     ` David Vrabel
2014-06-27 12:23       ` Ian Campbell
2014-06-27 12:51   ` Ian Campbell
2014-06-18 16:12 ` [PATCH 7/8] xl: generate a new random VM generation ID if requested David Vrabel
2014-06-18 16:12 ` [PATCH 8/8] docs: update docs for the ~/platform/generation-id key David Vrabel
2014-06-27 13:36 ` [PATCHv6 0/8] tools: rework VM Generation ID Ian Campbell
2014-06-30 18:31   ` Aravindh Puthiyaparambil (aravindp)
2014-07-02 19:53   ` Aravindh Puthiyaparambil (aravindp)
2014-07-03  8:52     ` Ian Campbell
2014-07-03 18:12       ` Aravindh Puthiyaparambil (aravindp)
  -- strict thread matches above, loose matches on Subject: below --
2014-06-12 15:04 [PATCHv5 " David Vrabel
2014-06-12 15:04 ` [PATCH 6/8] libxl: allow a generation ID to be specified at domain creation David Vrabel
2014-06-18  5:18   ` Hongyang Yang
2014-06-18  9:38     ` David Vrabel
2014-06-18  9:39       ` Ian Campbell
2014-06-18 11:33   ` Ian Campbell
2014-06-18 12:09     ` David Vrabel
2014-06-18 12:25       ` Ian Campbell
2014-06-18 13:22         ` David Vrabel

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=1403867762.25894.30.camel@kazak.uk.xensource.com \
    --to=ian.campbell@citrix.com \
    --cc=david.vrabel@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --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.