From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Clark Williams <williams@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Daniel Wagner <wagi@monom.org>,
RT <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RT] Warning from swake_up_all_locked in rt-4.4.4-rt11
Date: Wed, 30 Mar 2016 16:24:57 +0200 [thread overview]
Message-ID: <56FBE1B9.3080806@linutronix.de> (raw)
In-Reply-To: <20160330085218.32f13bd2@sluggy.hsv.redhat.com>
On 03/30/2016 03:52 PM, Clark Williams wrote:
> On Wed, 30 Mar 2016 12:22:51 +0200
> I'm seeing output like this with between 3 and 9 wakeups per kworker:
same here. And with
--- a/kernel/sched/swait.c
+++ b/kernel/sched/swait.c
@@ -32,17 +32,24 @@ EXPORT_SYMBOL(swake_up_locked);
void swake_up_all_locked(struct swait_queue_head *q)
{
struct swait_queue *curr;
+ char comms[512];
int wakes = 0;
+ comms[0] = '\0';
while (!list_empty(&q->task_list)) {
curr = list_first_entry(&q->task_list, typeof(*curr),
task_list);
+ strcat(comms, curr->task->comm);
+ strcat(comms, " ");
wake_up_process(curr->task);
list_del_init(&curr->task_list);
wakes++;
}
- WARN_ON(wakes > 2);
+ if (wakes > 2) {
+ pr_err("%s(%d) %d\n", __func__, __LINE__, wakes);
+ pr_err("%s(%d) %s\n", __func__, __LINE__, comms);
+ }
}
EXPORT_SYMBOL(swake_up_all_locked);
you would see that it wakes other kworker :)
Sebastian
next prev parent reply other threads:[~2016-03-30 14:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 3:53 [RT] Warning from swake_up_all_locked in rt-4.4.4-rt11 Clark Williams
2016-03-14 8:49 ` Thomas Gleixner
2016-03-30 10:22 ` Sebastian Andrzej Siewior
2016-03-30 13:52 ` Clark Williams
2016-03-30 14:24 ` Sebastian Andrzej Siewior [this message]
2016-04-01 10:33 ` Sebastian Andrzej Siewior
2016-04-03 3:44 ` Clark Williams
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=56FBE1B9.3080806@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=wagi@monom.org \
--cc=williams@redhat.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).