From: Wei Liu <wei.liu2@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: andrew.cooper3@citrix.com,
Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH] xen/time: fix gtime_to_gtsc for vtsc=1 PV guests
Date: Mon, 25 Apr 2016 14:28:50 +0100 [thread overview]
Message-ID: <20160425132850.GI11686@citrix.com> (raw)
In-Reply-To: <571E243E02000078000E550D@prv-mh.provo.novell.com>
On Mon, Apr 25, 2016 at 06:05:50AM -0600, Jan Beulich wrote:
> >>> On 25.04.16 at 13:18, <sstabellini@kernel.org> wrote:
> > From: Jan Beulich <JBeulich@suse.com>
> >
> > For vtsc=1 PV guests, rdtsc is trapped and calculated from get_s_time()
> > using gtime_to_gtsc. Similarly the tsc_timestamp, part of struct
> > vcpu_time_info, is calculated from stime_local_stamp using
> > gtime_to_gtsc.
> >
> > However gtime_to_gtsc can return 0, if time < vtsc_offset, which can
> > actually happen when gtime_to_gtsc is called passing stime_local_stamp
> > (the caller function is __update_vcpu_system_time).
> >
> > In that case the pvclock protocol doesn't work properly and the guest is
> > unable to calculate the system time correctly. As a consequence when the
> > guest tries to set a timer event (for example calling the
> > VCPUOP_set_singleshot_timer hypercall), the event will be in the past
> > causing Linux to hang.
> >
> > The purpose of the pvclock protocol is to allow the guest to calculate
> > the system_time in nanosec correctly. The guest calculates as follow:
> >
> > from_vtsc_scale(rdtsc - vcpu_time_info.tsc_timestamp) +
> > vcpu_time_info.system_time
> >
> > Given that with vtsc=1:
> > rdtsc = to_vtsc_scale(NOW() - vtsc_offset)
> > vcpu_time_info.tsc_timestamp = to_vtsc_scale(vcpu_time_info.system_time -
> > vtsc_offset)
> >
> > The expression evaluates to NOW(), which is what we want. However when
> > stime_local_stamp < vtsc_offset, vcpu_time_info.tsc_timestamp is
> > actually 0. As a consequence the calculated overall system_time is not
> > correct.
> >
> > This patch fixes the issue by letting gtime_to_gtsc return a negative
> > integer in the form of a wrapped around unsigned integer, thus when the
> > guest subtracts vcpu_time_info.tsc_timestamp from rdtsc will calculate
> > the right value.
> >
> > Signed-off-by: Jan Beulich <JBeulich@suse.com>
> > Signed-off-by: Stefano Stabellini <sstabellini@kernel.org>
>
> Assuming you mean for this to go into 4.7, I've added Wei to Cc
> (and you should do so in case of re-submission).
>
Release-acked-by: Wei Liu <wei.liu2@citrix.com>
(only skimmed the commit message)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-25 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 11:18 [PATCH] xen/time: fix gtime_to_gtsc for vtsc=1 PV guests Stefano Stabellini
2016-04-25 12:05 ` Jan Beulich
2016-04-25 12:19 ` Stefano Stabellini
2016-04-25 13:28 ` Wei Liu [this message]
2016-04-28 12:49 ` Andrew Cooper
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=20160425132850.GI11686@citrix.com \
--to=wei.liu2@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=sstabellini@kernel.org \
--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 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).