xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Paul Durrant <Paul.Durrant@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: Andrew Cooper <Andrew.Cooper3@citrix.com>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH 2/2] xen: Fix determining when domain creation is complete
Date: Tue, 13 Dec 2016 09:20:29 +0000	[thread overview]
Message-ID: <722b8532d11b4070a8c1b93a4bef3ca5@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <1481567384-32497-2-git-send-email-andrew.cooper3@citrix.com>

> -----Original Message-----
> From: Andrew Cooper [mailto:andrew.cooper3@citrix.com]
> Sent: 12 December 2016 18:30
> To: Xen-devel <xen-devel@lists.xen.org>
> Cc: Andrew Cooper <Andrew.Cooper3@citrix.com>; Jan Beulich
> <JBeulich@suse.com>; Paul Durrant <Paul.Durrant@citrix.com>; Boris
> Ostrovsky <boris.ostrovsky@oracle.com>
> Subject: [PATCH 2/2] xen: Fix determining when domain creation is complete
> 
> d->creation_finished is used in several places alter behaviour depending on
> whether the domain is being created, or is already running.
> 
> However, there is a latent bug if a toolstack component makes a pair of
> pause/unpause calls, where creation will be considered finished
> prematurely.
> 
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> ---
> CC: Jan Beulich <JBeulich@suse.com>
> CC: Paul Durrant <paul.durrant@citrix.com>

I tested this on initial boot and restore.

Tested-by: Paul Durrant <paul.durrant@citrix.com>

> CC: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> 
> This is probably a backport candidate, as creation_finished was introduced in
> 4.8
> ---
>  xen/common/domain.c | 21 ++++++++++++++-------
>  1 file changed, 14 insertions(+), 7 deletions(-)
> 
> diff --git a/xen/common/domain.c b/xen/common/domain.c
> index 3abaca9..05130e2 100644
> --- a/xen/common/domain.c
> +++ b/xen/common/domain.c
> @@ -1004,13 +1004,6 @@ int domain_unpause_by_systemcontroller(struct
> domain *d)
>  {
>      int old, new, prev = d->controller_pause_count;
> 
> -    /*
> -     * We record this information here for populate_physmap to figure out
> -     * that the domain has finished being created. In fact, we're only
> -     * allowed to set the MEMF_no_tlbflush flag during VM creation.
> -     */
> -    d->creation_finished = true;
> -
>      do
>      {
>          old = prev;
> @@ -1022,6 +1015,20 @@ int domain_unpause_by_systemcontroller(struct
> domain *d)
>          prev = cmpxchg(&d->controller_pause_count, old, new);
>      } while ( prev != old );
> 
> +    /*
> +     * d->controller_pause_count is initialised to 1, and the toolstack is
> +     * responsible for making one unpause hypercall when it wishes the guest
> +     * to start running.
> +     *
> +     * All other toolstack operations should make a pair of pause/unpause
> +     * calls and rely on the reference counting here.
> +     *
> +     * Creation is considered finished when the controller reference count
> +     * first drops to 0.
> +     */
> +    if ( new == 0 )
> +        d->creation_finished = true;
> +
>      domain_unpause(d);
> 
>      return 0;
> --
> 2.1.4


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

  parent reply	other threads:[~2016-12-13  9:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-12 18:29 [PATCH 1/2] x86/hvm: Fix HVMOP_get_param when skipping creating the default ioreq server Andrew Cooper
2016-12-12 18:29 ` [PATCH 2/2] xen: Fix determining when domain creation is complete Andrew Cooper
2016-12-13  8:19   ` Jan Beulich
2016-12-13  9:20   ` Paul Durrant [this message]
2016-12-13  9:44   ` Jan Beulich
2016-12-13  8:17 ` [PATCH 1/2] x86/hvm: Fix HVMOP_get_param when skipping creating the default ioreq server Jan Beulich
2016-12-13  9:21 ` 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=722b8532d11b4070a8c1b93a4bef3ca5@AMSPEX02CL03.citrite.net \
    --to=paul.durrant@citrix.com \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=boris.ostrovsky@oracle.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).