From: Paolo Bonzini <pbonzini@redhat.com>
To: Wanpeng Li <wanpeng.li@hotmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Cc: "Ingo Molnar" <mingo@kernel.org>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
"Rik van Riel" <riel@redhat.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Frederic Weisbecker" <fweisbec@gmail.com>,
"Radim Krčmář" <rkrcmar@redhat.com>
Subject: Re: [PATCH v4 3/3] sched/cputime: Add steal time support to full dynticks CPU time accounting
Date: Tue, 7 Jun 2016 12:47:53 +0200 [thread overview]
Message-ID: <56bdc61d-fed4-76bd-4e5f-5172ad0e20fa@redhat.com> (raw)
In-Reply-To: <SG2PR02MB15501BB06CAE47E4406FF7AD805D0@SG2PR02MB1550.apcprd02.prod.outlook.com>
On 07/06/2016 10:00, Wanpeng Li wrote:
> From: Wanpeng Li <wanpeng.li@hotmail.com>
>
> This patch adds guest steal-time support to full dynticks CPU
> time accounting. After the following commit:
>
> ff9a9b4c4334 ("sched, time: Switch VIRT_CPU_ACCOUNTING_GEN to jiffy granularity")
>
> ... time sampling became jiffy based, even if it's still listened
> to ring boundaries, so steal_account_process_tick() is reused
> to account how many 'ticks' are stolen-time, after the last accumulation.
I still have no idea how to parse this. What are "ring boundaries"?
Rik, can you suggest a better commit message?
> Suggested-and-Reviewed-by: Rik van Riel <riel@redhat.com>
Please split Suggested-by and Reviewed-by.
> diff --git a/kernel/sched/cputime.c b/kernel/sched/cputime.c
> index 75f98c5..9ff036b 100644
> --- a/kernel/sched/cputime.c
> +++ b/kernel/sched/cputime.c
> @@ -257,7 +257,7 @@ void account_idle_time(cputime_t cputime)
> cpustat[CPUTIME_IDLE] += (__force u64) cputime;
> }
>
> -static __always_inline bool steal_account_process_tick(void)
> +static __always_inline unsigned long steal_account_process_tick(void)
> {
> #ifdef CONFIG_PARAVIRT
> if (static_key_false(¶virt_steal_enabled)) {
> @@ -279,7 +279,7 @@ static __always_inline bool steal_account_process_tick(void)
> return steal_jiffies;
> }
> #endif
> - return false;
> + return 0;
> }
>
> /*
> @@ -691,9 +691,13 @@ static cputime_t get_vtime_delta(struct task_struct *tsk)
>
> static void __vtime_account_system(struct task_struct *tsk)
> {
> - cputime_t delta_cpu = get_vtime_delta(tsk);
> + cputime_t delta_time = get_vtime_delta(tsk);
> + cputime_t steal_time = jiffies_to_cputime(steal_account_process_tick());
>
> - account_system_time(tsk, irq_count(), delta_cpu, cputime_to_scaled(delta_cpu));
> + if (steal_time < delta_time) {
> + delta_time -= steal_time;
> + account_system_time(tsk, irq_count(), delta_time, cputime_to_scaled(delta_time));
> + }
> }
>
> void vtime_account_system(struct task_struct *tsk)
> @@ -718,13 +722,18 @@ void vtime_gen_account_irq_exit(struct task_struct *tsk)
>
> void vtime_account_user(struct task_struct *tsk)
> {
> - cputime_t delta_cpu;
> + cputime_t delta_time, steal_time;
>
> write_seqcount_begin(&tsk->vtime_seqcount);
> tsk->vtime_snap_whence = VTIME_SYS;
> if (vtime_delta(tsk)) {
> - delta_cpu = get_vtime_delta(tsk);
> - account_user_time(tsk, delta_cpu, cputime_to_scaled(delta_cpu));
> + delta_time = get_vtime_delta(tsk);
> + steal_time = jiffies_to_cputime(steal_account_process_tick());
> +
> + if (steal_time < delta_time) {
> + delta_time -= steal_time;
> + account_user_time(tsk, delta_time, cputime_to_scaled(delta_time));
> + }
> }
> write_seqcount_end(&tsk->vtime_seqcount);
> }
>
You're adding almost the same code to two callers of get_vtime_delta out
of three. I don't know the vtime accounting code very well, but why
doesn't the same apply to account_idle_time?
If it does, you should instead change get_vtime_delta to process steal
time and subtract it from the result.
Secondarily, when can it happen that steal_time > delta_time?
Thanks,
Paolo
next prev parent reply other threads:[~2016-06-07 10:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1465661590-4732-1-git-send-email-wanpeng.li@hotmail.com>
[not found] ` <SG2PR02MB15507073C531BAA82E9C8E67805D0@SG2PR02MB1550.apcprd02.prod.outlook.com>
2016-06-07 10:34 ` [PATCH v4 2/3] sched/cputime: Fix prev steal time accouting during cpu hotplug Paolo Bonzini
[not found] ` <SG2PR02MB15505ACED7653E515DE21620805D0@SG2PR02MB1550.apcprd02.prod.outlook.com>
2016-06-07 11:50 ` Fw: " Wanpeng Li
2016-06-07 11:53 ` Paolo Bonzini
[not found] ` <SG2PR02MB15501BB06CAE47E4406FF7AD805D0@SG2PR02MB1550.apcprd02.prod.outlook.com>
2016-06-07 10:47 ` Paolo Bonzini [this message]
2016-06-07 11:23 ` [PATCH v4 3/3] sched/cputime: Add steal time support to full dynticks CPU time accounting Wanpeng Li
2016-06-07 12:15 ` Wanpeng Li
2016-06-07 12:34 ` Paolo Bonzini
2016-06-07 8:33 [PATCH v4 1/3] KVM: fix steal clock warp during guest cpu hotplug Wanpeng Li
2016-06-07 8:33 ` [PATCH v4 3/3] sched/cputime: Add steal time support to full dynticks CPU time accounting Wanpeng Li
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=56bdc61d-fed4-76bd-4e5f-5172ad0e20fa@redhat.com \
--to=pbonzini@redhat.com \
--cc=fweisbec@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--cc=wanpeng.li@hotmail.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
all inboxes | Powered by JetHome®