From: Dario Faggioli <dario.faggioli@citrix.com>
To: Tony S <suokunstar@gmail.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
<xen-devel@lists.xenproject.org>, <linux-kernel@vger.kernel.org>
Cc: Juergen Gross <jgross@suse.com>, <sstabellini@kernel.org>,
David Vrabel <david.vrabel@citrix.com>,
George Dunlap <dunlapg@umich.edu>
Subject: Re: [Xen-devel] [PATCH] xen: add steal_clock support on x86
Date: Thu, 19 May 2016 05:36:17 +0200 [thread overview]
Message-ID: <1463628977.5851.53.camel@citrix.com> (raw)
In-Reply-To: <CAG2GYXE3GDmLPKZoTgQ7XKPOte-GshVCzhmD-Nuchbw15y2tRA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1711 bytes --]
On Wed, 2016-05-18 at 12:03 -0600, Tony S wrote:
> On Wed, May 18, 2016 at 11:59 AM, Tony S <suokunstar@gmail.com>
> wrote:
> > On Wed, May 18, 2016 at 11:20 AM, Boris Ostrovsky
> > <boris.ostrovsky@oracle.com> wrote:
> > > Tony narrowed the problem down to update_curr() where vruntime is
> > > calculated, based on runqueue's clock_task value. That value is
> > > computed
> > > in update_rq_clock_task(), which needs paravirt_steal_rq_enabled.
> > >
> > Hi Boris,
> >
> > You are right.
> >
> > The real problem is steal_clock in pv_time_ops is implemented in
> > KVM
> > but not in Xen.
> >
> > [...]
> >
> > Therefore, even though update_rq_clock_task() calculates the value
> > and
> > paravirt_steal_rq_enabled option is enabled, the steal value just
> > returns 0. This will cause the problem which I mentioned.
> >
> > update_rq_clock_task
> > --> paravirt_steal_clock
> > --> pv_time_ops.steal_clock
> > --> native_steal_clock (if in Xen)
> > --> 0
> >
Ok, thanks again for confirming this.
> Also, I tried the latest long term version of Linux 4.4, this issue
> still exists there. Hoping the next version can add this patch.
>
Yes, as Juergen said here:
http://lists.xen.org/archives/html/xen-devel/2016-05/msg01712.html
he has in his plans to implement the full mechanism. It will just take
a bit longer, due to the amount of work necessary for this second part.
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-05-19 3:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 12:15 [PATCH] xen: add steal_clock support on x86 Juergen Gross
2016-05-18 14:46 ` Boris Ostrovsky
2016-05-18 14:53 ` Juergen Gross
2016-05-18 15:25 ` Boris Ostrovsky
2016-05-18 15:42 ` Juergen Gross
2016-05-18 15:45 ` David Vrabel
2016-05-18 15:51 ` Juergen Gross
2016-05-18 15:52 ` David Vrabel
2016-05-18 15:53 ` Boris Ostrovsky
2016-05-18 16:00 ` Juergen Gross
2016-05-18 16:13 ` Boris Ostrovsky
2016-05-19 5:33 ` Juergen Gross
2016-05-18 16:10 ` [Xen-devel] " Dario Faggioli
2016-05-18 17:20 ` Boris Ostrovsky
2016-05-18 17:59 ` Tony S
2016-05-18 18:03 ` Tony S
2016-05-19 3:36 ` Dario Faggioli [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=1463628977.5851.53.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=dunlapg@umich.edu \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@kernel.org \
--cc=suokunstar@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox