From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Thomas Pfaff <tpfaff@pcs.com>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
"rostedt@goodmis.org" <rostedt@goodmis.org>
Subject: Re: [PATCH 3.4.62-rt77] fix irq thread scheduling
Date: Fri, 11 Oct 2013 12:58:12 +0200 [thread overview]
Message-ID: <20131011105812.GF6983@linutronix.de> (raw)
In-Reply-To: <alpine.LNX.2.00.1310081550340.16551@lxtpfaff.pcs.ditec.de>
* Thomas Pfaff | 2013-10-08 15:58:50 [+0200]:
>I did a quick check with 3.10.14-rt9 and it is not affected, because
>sched_setscheduler is called in the context of the irq thread as the mainline
>kernel does, but the 3.6 rt patch moved this into __setup_irq.
Thanks for that report. It looks that this is broken upstream as well.
I'm going to merge the patch that broke it, your fix and try to do the
same for upstream.
>Thomas
Sebastian
prev parent reply other threads:[~2013-10-11 10:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 9:02 [PATCH 3.4.62-rt77] fix irq thread scheduling Thomas Pfaff
2013-10-04 14:05 ` Sebastian Andrzej Siewior
2013-10-08 13:58 ` Thomas Pfaff
2013-10-08 14:12 ` Thomas Pfaff
2013-10-11 10:58 ` 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=20131011105812.GF6983@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tpfaff@pcs.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).