mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Muchun Song <songmuchun@bytedance.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: mingo@redhat.com, Peter Zijlstra <peterz@infradead.org>,
	juri.lelli@redhat.com,
	Vincent Guittot <vincent.guittot@linaro.org>,
	dietmar.eggemann@arm.com, Benjamin Segall <bsegall@google.com>,
	mgorman@suse.de, mingo@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [External] Re: [PATCH] sched/cpuacct: Fix charge cpuacct.usage_sys incorrently.
Date: Fri, 17 Apr 2020 11:11:34 +0800	[thread overview]
Message-ID: <CAMZfGtVWMUTP4AYch_dAPWRNazmJ7wkMODgqcqS8rhCZPLf+Jg@mail.gmail.com> (raw)
In-Reply-To: <20200416120132.7c2df52a@gandalf.local.home>

On Fri, Apr 17, 2020 at 12:01 AM Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Thu, 16 Apr 2020 11:35:02 -0400
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > On Thu, 16 Apr 2020 22:18:33 +0800
> > Muchun Song <songmuchun@bytedance.com> wrote:
> >
> > > The user_mode(task_pt_regs(tsk)) always return true for
> > > user thread, and false for kernel thread. So it means that
> > > the cpuacct.usage_sys is the time that kernel thread uses
> > > not the time that thread uses in the kernel mode. We can
> > > use get_irq_regs() instead of task_pt_regs() to fix it.
> > >
> > > Signed-off-by: Muchun Song <songmuchun@bytedance.com>
> > > ---
> > >  kernel/sched/cpuacct.c | 3 ++-
> > >  1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/kernel/sched/cpuacct.c b/kernel/sched/cpuacct.c
> > > index 6448b0438ffb2..edfc62554648e 100644
> > > --- a/kernel/sched/cpuacct.c
> > > +++ b/kernel/sched/cpuacct.c
> > > @@ -5,6 +5,7 @@
> > >   * Based on the work by Paul Menage (menage@google.com) and Balbir Singh
> > >   * (balbir@in.ibm.com).
> > >   */
> > > +#include <asm/irq_regs.h>
> > >  #include "sched.h"
> > >
> > >  /* Time spent by the tasks of the CPU accounting group executing in ... */
> > > @@ -339,7 +340,7 @@ void cpuacct_charge(struct task_struct *tsk, u64 cputime)
> > >  {
> > >     struct cpuacct *ca;
> > >     int index = CPUACCT_STAT_SYSTEM;
> > > -   struct pt_regs *regs = task_pt_regs(tsk);
> > > +   struct pt_regs *regs = get_irq_regs();
> >
> > But get_irq_regs() is only available from interrupt context. This will be
> > NULL most the time, whereas the original way will have regs existing for
> > the task.
>
> Perhaps you want:
>
>         regs = get_irqs_regs();
>         if (!regs)
>                 regs = task_pt_regs(tsk);
>
> ?

Yeah, If regs is NULL, we can get it fall back to task_pt_regs.
Does Anyone else have suggestions?

>
> -- Steve
>
> >
> > >
> > >     if (regs && user_mode(regs))
> > >             index = CPUACCT_STAT_USER;
> >

-- 
Yours,
Muchun

  reply	other threads:[~2020-04-17  3:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16 14:18 Muchun Song
2020-04-16 15:35 ` Steven Rostedt
2020-04-16 16:01   ` Steven Rostedt
2020-04-17  3:11     ` Muchun Song [this message]
2020-04-17  3:07   ` [External] " Muchun Song

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=CAMZfGtVWMUTP4AYch_dAPWRNazmJ7wkMODgqcqS8rhCZPLf+Jg@mail.gmail.com \
    --to=songmuchun@bytedance.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.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®