From: Rik van Riel <riel@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>,
Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Ingo Molnar <mingo@kernel.org>,
Dongli Zhang <dongli.zhang@oracle.com>,
Wanpeng Li <wanpeng.li@hotmail.com>,
Xiaolong Ye <xiaolong.ye@intel.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xen.org,
mingo@redhat.com, dario.faggioli@citrix.com, bevan@bi-co.net,
xen.list@daevel.fr, joao.m.martins@oracle.com
Subject: Re: [PATCH 1/1] sched/cputime: do not decrease steal time after live migration on xen
Date: Tue, 10 Oct 2017 10:01:02 -0400 [thread overview]
Message-ID: <1507644062.21121.179.camel@redhat.com> (raw)
In-Reply-To: <20171010124816.ujbjwqow4axpzgk2@hirez.programming.kicks-ass.net>
On Tue, 2017-10-10 at 14:48 +0200, Peter Zijlstra wrote:
> On Tue, Oct 10, 2017 at 02:42:01PM +0200, Stanislaw Gruszka wrote:
> > > > + u64 steal, steal_time;
> > > > + s64 steal_delta;
> > > > +
> > > > + steal_time =
> > > > paravirt_steal_clock(smp_processor_id());
> > > > + steal = steal_delta = steal_time - this_rq()-
> > > > >prev_steal_time;
> > > > +
> > > > + if (unlikely(steal_delta < 0)) {
> > > > + this_rq()->prev_steal_time =
> > > > steal_time;
> >
> > I don't think setting prev_steal_time to smaller value is right
> > thing to do.
> >
> > Beside, I don't think we need to check for overflow condition for
> > cputime variables (it will happen after 279 years :-). So instead
> > of introducing signed steal_delta variable I would just add
> > below check, which should be sufficient to fix the problem:
> >
> > if (unlikely(steal <= this_rq()->prev_steal_time))
> > return 0;
>
> How about you just fix up paravirt_steal_time() on migration and not
> muck with the users ?
Not just migration, either. CPU hotplug is another time to fix up
the steal time.
next prev parent reply other threads:[~2017-10-10 14:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 9:14 Dongli Zhang
2017-10-10 10:07 ` [Xen-devel] " Jan Beulich
2017-10-10 10:59 ` Ingo Molnar
2017-10-10 12:42 ` Stanislaw Gruszka
2017-10-10 12:48 ` Peter Zijlstra
2017-10-10 14:01 ` Rik van Riel [this message]
2017-10-11 7:47 ` Dongli Zhang
2017-10-11 7:29 ` Dongli Zhang
2017-10-10 11:58 ` Peter Zijlstra
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=1507644062.21121.179.camel@redhat.com \
--to=riel@redhat.com \
--cc=bevan@bi-co.net \
--cc=dario.faggioli@citrix.com \
--cc=dongli.zhang@oracle.com \
--cc=fweisbec@gmail.com \
--cc=joao.m.martins@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sgruszka@redhat.com \
--cc=wanpeng.li@hotmail.com \
--cc=xen-devel@lists.xen.org \
--cc=xen.list@daevel.fr \
--cc=xiaolong.ye@intel.com \
/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
Powered by JetHome