From: Tejun Heo <tj@kernel.org>
To: Andrey Ryabinin <arbn@yandex-team.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Daniel Jordan <daniel.m.jordan@oracle.com>,
stable@vger.kernel.org, Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
Dan Schatzberg <schatzberg.dan@gmail.com>
Subject: Re: [PATCH v3 1/4] cputime, cpuacct: Include guest time in user time in cpuacct.stat
Date: Mon, 15 Nov 2021 11:06:16 -1000 [thread overview]
Message-ID: <YZLLyFnT95o4Sa8X@slm.duckdns.org> (raw)
In-Reply-To: <20211115164607.23784-1-arbn@yandex-team.com>
Hello,
Ingo, Peter, this looks fine to be sans a couple typos in the descriptions.
Please let me know if you wanna take them through sched tree. Otherwise,
I'll route them through cgroup tree in a few days.
Thanks.
--
tejun
next prev parent reply other threads:[~2021-11-16 0:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 16:46 Andrey Ryabinin
2021-11-15 16:46 ` [PATCH v3 2/4] cpuacct: convert BUG_ON() to WARN_ON_ONCE() Andrey Ryabinin
2021-11-23 11:01 ` [tip: sched/core] cpuacct: Convert " tip-bot2 for Andrey Ryabinin
2021-11-15 16:46 ` [PATCH v3 3/4] sched/cpuacct: fix user/system in shown cpuacct.usage* Andrey Ryabinin
2021-11-23 11:01 ` [tip: sched/core] sched/cpuacct: Fix " tip-bot2 for Andrey Ryabinin
2021-11-15 16:46 ` [PATCH v3 4/4] sched/cpuacct: Make user/system times in cpuacct.stat more precise Andrey Ryabinin
2021-11-23 11:01 ` [tip: sched/core] " tip-bot2 for Andrey Ryabinin
2021-11-15 21:06 ` Tejun Heo [this message]
2021-11-18 14:29 ` [PATCH v3 1/4] cputime, cpuacct: Include guest time in user time in cpuacct.stat Peter Zijlstra
2021-11-23 11:01 ` [tip: sched/core] " tip-bot2 for Andrey Ryabinin
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=YZLLyFnT95o4Sa8X@slm.duckdns.org \
--to=tj@kernel.org \
--cc=arbn@yandex-team.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=cgroups@vger.kernel.org \
--cc=daniel.m.jordan@oracle.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=schatzberg.dan@gmail.com \
--cc=stable@vger.kernel.org \
--cc=vincent.guittot@linaro.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
all inboxes | Powered by JetHome®