From: Peter Zijlstra <peterz@infradead.org>
To: Henrik Austad <henrik@austad.us>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Henrik Austad <haustad@cisco.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
John Stultz <john.stultz@linaro.org>
Subject: Re: [PATCH Resend] Expose do_timer CPU via sysctl to userspace as R/W
Date: Wed, 19 Feb 2014 20:50:44 +0100 [thread overview]
Message-ID: <20140219195044.GZ14089@laptop.programming.kicks-ass.net> (raw)
In-Reply-To: <20140219194355.GA23228@austad.us>
On Wed, Feb 19, 2014 at 08:43:55PM +0100, Henrik Austad wrote:
> The online-part should be taken care of by the cpu_present(), no?
No, cpu_present() only means there is a physical CPU present. It might
be offline.
See the comment in include/linux/cpumask.h
prev parent reply other threads:[~2014-02-19 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 12:32 henrik
2014-02-19 16:42 ` Thomas Gleixner
2014-02-19 19:43 ` Henrik Austad
2014-02-19 19:50 ` Peter Zijlstra [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=20140219195044.GZ14089@laptop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=fweisbec@gmail.com \
--cc=haustad@cisco.com \
--cc=henrik@austad.us \
--cc=john.stultz@linaro.org \
--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®