From: Yunhong Jiang <yunhong.jiang@linux.intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nohz: make the idle_entrytime/idle_exittime correct
Date: Fri, 18 Sep 2015 11:42:13 -0700 [thread overview]
Message-ID: <20150918184213.GA31162@jnakajim-build> (raw)
In-Reply-To: <alpine.DEB.2.11.1509172344140.3951@nanos>
On Thu, Sep 17, 2015 at 11:45:37PM +0200, Thomas Gleixner wrote:
> On Wed, 16 Sep 2015, Yunhong Jiang wrote:
>
> > Currently the idle_entrytime is updated on idle_entry, idle_exit and
> > get_cpu_idle/iowait_time_us() with non-NULL parameter. This makes the
> > idle_entrytime not the real entrytime anymore. The idle_exittiime is
> > updated when exit tickless state, which can be idle tickless or full
> > tickless.
>
> If something calls one of the functions then the cpu is not idle. It's
> running code.
I think the get_cpu_idle/iowait_time_us() can be called from other CPUs.
Hmm, I should state this patch as "no idle_entrytime update on
get_cpu_idle/iowait_time_us()". If you think this statement is correct,
I will re-submit a patch for it.
>
> > Change the idle_entrytime to be updated only when enter idle, the
> > idle_exittime to be updated only when exit idle. Update
> > the get_cpu_idle_iowait_time_us() accordingly.
>
> And the rationale for this change is?
I tried to check /proc/timer_list for idle_entrytime/idle_exittime, and
noticed this when reading the corresponding code. So no special reason for
this change, just correctness.
Thanks
--jyh
>
> Thanks,
>
> tglx
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2015-09-18 18:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 23:19 Yunhong Jiang
2015-09-17 21:45 ` Thomas Gleixner
2015-09-18 18:42 ` Yunhong Jiang [this message]
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=20150918184213.GA31162@jnakajim-build \
--to=yunhong.jiang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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®