From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Ye Xiaolong <xiaolong.ye@intel.com>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
lkp@01.org
Subject: Re: [lkp] [rcu] a7410f28ce: INFO: rcu_sched detected expedited stalls on CPUs/tasks: { 0-... } 25089 jiffies s: 9 root: 0x1/.
Date: Tue, 29 Nov 2016 09:18:27 +0100 [thread overview]
Message-ID: <20161129081827.sxehpqxmmolagga2@linutronix.de> (raw)
In-Reply-To: <20161128173457.GJ2501@yexl-desktop>
On 2016-11-29 01:34:57 [+0800], Ye Xiaolong wrote:
> Thanks for the explanation, we'll ignore this kind of reports. And sorry for
> the noise.
This is "special" because my patch enabled the "expedited" RCU on its
own. This kind of report against a network driver (for instance) would
probably mean a problem in the patch itself.
> Thanks,
> Xiaolong
Sebastian
prev parent reply other threads:[~2016-11-29 8:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 6:25 [lkp] [rcu] a7410f28ce: INFO: rcu_sched detected expedited stalls on CPUs/tasks: { 0-... } 25089 jiffies s: 9 root: 0x1/ kernel test robot
2016-11-28 20:53 ` Sebastian Andrzej Siewior
2016-11-28 17:34 ` Ye Xiaolong
2016-11-29 8:18 ` Sebastian Andrzej Siewior [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=20161129081827.sxehpqxmmolagga2@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=xiaolong.ye@intel.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;
as well as URLs for NNTP newsgroup(s).