From: Tom Li <tomli@tomli.me>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: paulmck@linux.ibm.com, ak@linux.intel.com, bp@alien8.de,
hpa@zytor.com, linux-kernel@vger.kernel.org, mingo@redhat.com,
rjw@rjwysocki.net, ville.syrjala@linux.intel.com,
viresh.kumar@linaro.org, linux-mips@vger.kernel.org
Subject: Re: [REGRESSION 4.20-rc1] 45975c7d21a1 ("rcu: Define RCU-sched API in terms of RCU for Tree RCU PREEMPT builds")
Date: Tue, 5 Feb 2019 21:05:59 +0800 [thread overview]
Message-ID: <20190205130559.GA12858@localhost.localdomain> (raw)
In-Reply-To: <20190205095809.GA16356@darkstar.musicnaut.iki.fi>
On Tue, Feb 05, 2019 at 11:58:09AM +0200, Aaro Koskinen wrote:
> Can you try below fix? It works on my Loongson.
Hello Aaro, thanks for your response. But in case you've missed
the original thread, please check it at:
https://lkml.org/lkml/2018/11/13/857
My problem is NOT about how to fix the problem on Loongson (or
x86): the patch in the original thread (only has one-line-of-code,
simply changes timing of cpufreq_core_init), or your patch, is
indeed working. But they are workarounds, the real issue is the race
condition in cpufreq.
My question is
1. What's the progress and current consensus about how the underlying
problem can be fixed.
2. If there's no consensus since November, is it possible that we land
a hotfix patch to linux-stable as a temporary workaround?
Cheers,
Tom Li.
next prev parent reply other threads:[~2019-02-05 13:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181113135453.GW9144@intel.com>
[not found] ` <20181113151037.GG4170@linux.ibm.com>
[not found] ` <20181114202013.GA27603@linux.ibm.com>
[not found] ` <20181126220122.GA6345@linux.ibm.com>
2019-02-05 5:07 ` [REGRESSION 4.20-rc1] 45975c7d21a1 ("rcu: Define RCU-sched API in terms of RCU for Tree RCU PREEMPT builds") Tom Li
2019-02-05 9:58 ` Aaro Koskinen
2019-02-05 13:05 ` Tom Li [this message]
2019-02-05 18:59 ` Aaro Koskinen
2019-02-06 1:22 ` tomli
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=20190205130559.GA12858@localhost.localdomain \
--to=tomli@tomli.me \
--cc=aaro.koskinen@iki.fi \
--cc=ak@linux.intel.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@linux.ibm.com \
--cc=rjw@rjwysocki.net \
--cc=ville.syrjala@linux.intel.com \
--cc=viresh.kumar@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;
as well as URLs for NNTP newsgroup(s).