From: Sudeep Holla <sudeep.holla@arm.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: Sudeep Holla <sudeep.holla@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Santosh Shilimkar <ssantosh@kernel.org>
Subject: Re: [PATCH 1/3] clocksource: drivers: set clockevent device cpumask to cpu_possible_mask
Date: Wed, 11 Jul 2018 14:42:34 +0100 [thread overview]
Message-ID: <229f0ac1-16b5-3fcf-3d0d-60ad59ea40f8@arm.com> (raw)
In-Reply-To: <2009eeb1-e925-fe5c-ac4a-9f3e41945127@linaro.org>
Hi Daniel,
On 11/07/18 12:36, Daniel Lezcano wrote:
> On 11/07/2018 13:24, Sudeep Holla wrote:
>> Currently, quite a few clockevent devices have cpumask set to
>> cpu_all_mask which should be fine. However, cpu_possible_mask is more
>> accurate and if there are any other clockevent devices in the system
>> which have cpumask set to cpu_possible_mask, then having cpu_all_mask
>> may result in issues (mostly boot hang with forever loops in
>> clockevents_notify_released).
>>
>> So, lets replace all the clockevent device cpu_all_mask to
>> cpu_possible_mask in order to prevent above mentioned possible issue.
>>
>> Cc: Daniel Lezcano <daniel.lezcano@linaro.org>
>> Cc: Thomas Gleixner <tglx@linutronix.de>
>> Cc: Thierry Reding <thierry.reding@gmail.com>
>> Cc: Jonathan Hunter <jonathanh@nvidia.com>
>> Cc: Santosh Shilimkar <ssantosh@kernel.org>
>> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
>> ---
>
> Applied, thanks for the fix.
>
Thomas was planning to take this, see [1]
--
Regards,
Sudeep
[1]
https://lore.kernel.org/lkml/alpine.DEB.2.21.1807102220320.1588@nanos.tec.linutronix.de/
next prev parent reply other threads:[~2018-07-11 13:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 11:24 Sudeep Holla
2018-07-11 11:24 ` [PATCH 2/3] tick: broadcast-hrtimer: use cpu_possible_mask for ce_broadcast_hrtimer Sudeep Holla
2018-08-02 12:58 ` [tip:timers/core] tick/broadcast-hrtimer: Use " tip-bot for Sudeep Holla
2018-07-11 11:24 ` [PATCH 3/3] clockevents: warn if cpu_all_mask is used for cpumask while registering new device Sudeep Holla
2018-08-02 12:39 ` Sudeep Holla
2018-08-02 12:58 ` [tip:timers/core] clockevents: Warn if cpu_all_mask is used as cpumask tip-bot for Sudeep Holla
2018-07-11 11:36 ` [PATCH 1/3] clocksource: drivers: set clockevent device cpumask to cpu_possible_mask Daniel Lezcano
2018-07-11 13:42 ` Sudeep Holla [this message]
2018-07-11 16:38 ` Daniel Lezcano
2018-07-13 22:45 ` Thomas Gleixner
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=229f0ac1-16b5-3fcf-3d0d-60ad59ea40f8@arm.com \
--to=sudeep.holla@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ssantosh@kernel.org \
--cc=tglx@linutronix.de \
--cc=thierry.reding@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®