From: Thomas Gleixner <tglx@linutronix.de>
To: William Breathitt Gray <vilhelm.gray@gmail.com>
Cc: linux-kernel@vger.kernel.org, john.stultz@linaro.org
Subject: Re: Regarding USER_HZ and the exposure of kernel jiffies in userspace
Date: Sat, 22 Aug 2015 16:29:27 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1508221626340.3873@nanos> (raw)
In-Reply-To: <55D880F3.4030909@gmail.com>
On Sat, 22 Aug 2015, William Breathitt Gray wrote:
> I believe the error in my understanding is the assumption that _all_
> instances of kernel jiffies exposure in userspace should be scaled; but
> it appears that not all instances are. When are kernel jiffies meant to
> be scaled via USER_HZ, and when are they not?
All instances which are de facto APIs, syscalls and also various files
in proc/ must be in USER_HZ because userspace applications depend on
the USER_HZ value.
proc/timer_list is exempt from that because its more a debugging
interface which is not part of the strict kernel API. And we really
want to see the real values and not the scaled USER_HZ ones for that
purpose. I hope that answers your question.
Thanks,
tglx
prev parent reply other threads:[~2015-08-22 14:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-22 14:02 William Breathitt Gray
2015-08-22 14:29 ` Thomas Gleixner [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=alpine.DEB.2.11.1508221626340.3873@nanos \
--to=tglx@linutronix.de \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vilhelm.gray@gmail.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®