All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dongli Zhang <dongli.zhang@oracle.com>
To: Rik van Riel <riel@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Ingo Molnar <mingo@kernel.org>,
	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: Wed, 11 Oct 2017 15:47:44 +0800	[thread overview]
Message-ID: <6217d9be-8c33-3c8d-31d6-3daa59318ed8@oracle.com> (raw)
In-Reply-To: <1507644062.21121.179.camel@redhat.com>

Hi Rik,

On 10/10/2017 10:01 PM, Rik van Riel wrote:
> 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.

I think this issue might be hit when we add and online vcpu after a very very
long time since boot (or the last time vcpu is offline). Please correct me if I
am wrong.

Thank you very much!

Dongli Zhang

> 

  parent reply	other threads:[~2017-10-11  7:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-10  9:14 [PATCH 1/1] sched/cputime: do not decrease steal time after live migration on xen Dongli Zhang
2017-10-10 10:07 ` Jan Beulich
2017-10-10 10:07 ` [Xen-devel] " Jan Beulich
2017-10-10 10:59 ` Ingo Molnar
2017-10-10 10:59 ` Ingo Molnar
2017-10-10 12:42   ` Stanislaw Gruszka
2017-10-10 12:42   ` Stanislaw Gruszka
2017-10-10 12:48     ` Peter Zijlstra
2017-10-10 12:48     ` Peter Zijlstra
2017-10-10 14:01       ` Rik van Riel
2017-10-10 14:01       ` Rik van Riel
2017-10-11  7:47         ` Dongli Zhang
2017-10-11  7:47         ` Dongli Zhang [this message]
2017-10-11  7:29     ` Dongli Zhang
2017-10-11  7:29     ` Dongli Zhang
2017-10-10 11:58 ` Peter Zijlstra
2017-10-10 11:58 ` Peter Zijlstra
2017-10-10  9:14 Dongli Zhang

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=6217d9be-8c33-3c8d-31d6-3daa59318ed8@oracle.com \
    --to=dongli.zhang@oracle.com \
    --cc=bevan@bi-co.net \
    --cc=dario.faggioli@citrix.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=riel@redhat.com \
    --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 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.