xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Roger Pau Monne <roger.pau@citrix.com>
Cc: Keir Fraser <keir@xen.org>, Jan Beulich <JBeulich@suse.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH v2] xen: fix initialization of wallclock time for PVHVM on migration
Date: Wed, 12 Jun 2013 11:06:33 +0100	[thread overview]
Message-ID: <51B84829.4070705@eu.citrix.com> (raw)
In-Reply-To: <1370968885-6644-1-git-send-email-roger.pau@citrix.com>

On 11/06/13 17:41, Roger Pau Monne wrote:
> Call update_domain_wallclock_time on hvm_latch_shinfo_size even if
> the bitness of the guest has already been set, this fixes the problem
> with the wallclock not being set for PVHVM guests on resume from
> migration.
>
> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
> Cc: Jan Beulich <JBeulich@suse.com>
> Cc: Keir Fraser <keir@xen.org>
> Cc: George Dunlap <George.Dunlap@eu.citrix.com>

Re the release:

Acked-by: George Dunlap <george.dunlap@eu.citrix.com>

> ---
> Since this is a bug fix, I think it is suitable for inclusion in the
> 4.3 release, and backported to older releases.
> ---
>   xen/arch/x86/hvm/hvm.c |   20 ++++++--------------
>   1 files changed, 6 insertions(+), 14 deletions(-)
>
> diff --git a/xen/arch/x86/hvm/hvm.c b/xen/arch/x86/hvm/hvm.c
> index a962ce2..0dcfd81 100644
> --- a/xen/arch/x86/hvm/hvm.c
> +++ b/xen/arch/x86/hvm/hvm.c
> @@ -3404,21 +3404,13 @@ static void hvm_latch_shinfo_size(struct domain *d)
>        */
>       if ( current->domain == d ) {
>           new_has_32bit = (hvm_guest_x86_mode(current) != 8);
> -        if (new_has_32bit != d->arch.has_32bit_shinfo) {
> +        if (new_has_32bit != d->arch.has_32bit_shinfo)
>               d->arch.has_32bit_shinfo = new_has_32bit;
> -            /*
> -             * Make sure that the timebase in the shared info
> -             * structure is correct for its new bit-ness.  We should
> -             * arguably try to convert the other fields as well, but
> -             * that's much more problematic (e.g. what do you do if
> -             * you're going from 64 bit to 32 bit and there's an event
> -             * channel pending which doesn't exist in the 32 bit
> -             * version?).  Just setting the wallclock time seems to be
> -             * sufficient for everything we do, even if it is a bit of
> -             * a hack.
> -             */
> -            update_domain_wallclock_time(d);
> -        }
> +        /*
> +         * Make sure that the timebase in the shared info
> +         * structure is correct.
> +         */
> +        update_domain_wallclock_time(d);
>       }
>   }
>   


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

      parent reply	other threads:[~2013-06-12 10:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-11 16:41 [PATCH v2] xen: fix initialization of wallclock time for PVHVM on migration Roger Pau Monne
2013-06-11 17:02 ` Keir Fraser
2013-06-11 18:09   ` Andrew Cooper
2013-06-12  7:41     ` Jan Beulich
2013-06-12 11:25       ` Andrew Cooper
2013-06-12  9:36     ` Keir Fraser
2013-06-12 11:29       ` Andrew Cooper
2013-06-12  7:42   ` Jan Beulich
2013-06-12 10:06 ` George Dunlap [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=51B84829.4070705@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=keir@xen.org \
    --cc=roger.pau@citrix.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).