All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kouya Shimura <kouya@jp.fujitsu.com>
To: Alex Bligh <alex@alex.org.uk>
Cc: Tim Deegan <tim@xen.org>, Diana Crisan <dcrisan@flexiant.com>,
	Keir Fraser <keir@xen.org>, Jan Beulich <JBeulich@suse.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH 2/2] x86/hvm: fix corrupt ACPI PM-Timer during live migration
Date: Thu, 16 May 2013 14:29:00 +0900	[thread overview]
Message-ID: <51946E9C.5070204@jp.fujitsu.com> (raw)
In-Reply-To: <5193BDAB02000078000D688A@nat28.tlf.novell.com>

On 05/15/2013 11:54 PM, Jan Beulich wrote:
>>>> On 15.05.13 at 16:49, Alex Bligh <alex@alex.org.uk> wrote:
>> --On 15 May 2013 15:31:19 +0100 Jan Beulich <JBeulich@suse.com> wrote:
>>
>>>> Did this ever get committed? I can't immediately find a commit.
>>>
>>> No, it didn't - no-one knowing that code well enough ever acked
>>> patch 1, and without that we can't apply the patch here.
>>
>> I certainly am not someone who knows that code well, so can't help
>> with that. But I (or more accurately Diana) can reliably replicate
>> live migrate on HVM and qemu-upstream DM causing (a) ACPI entries
>> to disappear from xenstore and (b) walltime to fail to advance in
>> the migrated domain until the walltime is manually set (stuck
>> clock).
>>
>> Is this likely to be related?
>
> I'd like to defer to Kouya to tell whether that matches the
> symptoms he saw.

I don't think my fix is related to Alex's problem.
I observed that gettimeofday() sometimes goes backward *a few seconds*
on migration.

In linux OSs, ACPI Timer value is masked by 24bit.
The valid range:
      (1 / 3.579545MHz) * 0xffffff = 4.7sec
So, the effect of the corrupt ACPI timer is at most 4.7 sec.
The clock shouldn't be frozen for a long time.

Apparently (a) sounds like a problem of xl toolstack.

--
Kouya

  reply	other threads:[~2013-05-16  5:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-05  6:12 [PATCH] x86/hvm: fix corrupt ACPI PM-Timer during live migration Kouya Shimura
2013-02-12 12:26 ` Jan Beulich
2013-02-14  6:09   ` Kouya Shimura
2013-02-15 16:45     ` Jan Beulich
2013-02-20  7:42       ` Kouya Shimura
2013-03-07 15:58         ` Jan Beulich
2013-03-08  7:59           ` Kouya Shimura
2013-03-21  7:31           ` Kouya Shimura
2013-03-21  8:05             ` Jan Beulich
     [not found]           ` <514A9BC4.40508@jp.fujitsu.com>
2013-03-21  7:32             ` [PATCH 1/2] x86/hvm: prevent guest's timers from going backwards, when timer_mode=0 Kouya Shimura
2013-03-21  7:32             ` [PATCH 2/2] x86/hvm: fix corrupt ACPI PM-Timer during live migration Kouya Shimura
2013-03-21 10:01               ` Jan Beulich
2013-03-22  1:12                 ` Kouya Shimura
2013-03-22  8:02                   ` Jan Beulich
2013-05-15 14:23                     ` Alex Bligh
2013-05-15 14:31                       ` Jan Beulich
2013-05-15 14:49                         ` Alex Bligh
2013-05-15 14:54                           ` Jan Beulich
2013-05-16  5:29                             ` Kouya Shimura [this message]
2013-05-16 10:38                               ` Alex Bligh
2013-05-16  5:27                         ` Kouya Shimura
2013-05-16  9:54                           ` Tim Deegan

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=51946E9C.5070204@jp.fujitsu.com \
    --to=kouya@jp.fujitsu.com \
    --cc=JBeulich@suse.com \
    --cc=alex@alex.org.uk \
    --cc=dcrisan@flexiant.com \
    --cc=keir@xen.org \
    --cc=tim@xen.org \
    --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 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.