From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 3.10.4-rt1
Date: Fri, 2 Aug 2013 10:19:36 -0400 [thread overview]
Message-ID: <20130802141936.GA8267@windriver.com> (raw)
In-Reply-To: <51FBA9CC.2090206@linutronix.de>
[Re: [ANNOUNCE] 3.10.4-rt1] On 02/08/2013 (Fri 14:45) Sebastian Andrzej Siewior wrote:
> On 08/02/2013 07:05 AM, Benjamin Herrenschmidt wrote:
> > On Thu, 2013-08-01 at 20:03 -0400, Paul Gortmaker wrote:
> >> I've added Ben to the CC in case he has a suggestion on
> >> how best to fix this, even though it is not yet mainline.
> >
> > Can you exchange with a TIF_ that isn't used in asm ? For example
> > TIF_PERFMON_* ? Keep all the asm ones below 16 and move up the ones
> > that are used in C only ?
>
> I going to look later at this. I think I swapped one of the TIF_
> defines in v3.8 so it should work.
Yep, 3.8 shuffled TIF_MEMDIE to the end of the queue, but
in 3.10, mainline commit 22ecbe8dcef has already done that trick.
The list of donor victims that aren't used in asm is getting
smaller, but TIF_POLLING_NRFLAG seems OK and it puts RESCHED
and RESCHED_LAZY right beside each other.
Thanks guys,
Paul.
--
diff --git a/arch/powerpc/include/asm/thread_info.h b/arch/powerpc/include/asm/thread_info.h
index 2469444..f50711f 100644
--- a/arch/powerpc/include/asm/thread_info.h
+++ b/arch/powerpc/include/asm/thread_info.h
@@ -92,8 +92,7 @@ static inline struct thread_info *current_thread_info(void)
#define TIF_SYSCALL_TRACE 0 /* syscall trace active */
#define TIF_SIGPENDING 1 /* signal pending */
#define TIF_NEED_RESCHED 2 /* rescheduling necessary */
-#define TIF_POLLING_NRFLAG 3 /* true if poll_idle() is polling
- TIF_NEED_RESCHED */
+#define TIF_NEED_RESCHED_LAZY 3 /* lazy rescheduling necessary */
#define TIF_32BIT 4 /* 32 bit binary */
#define TIF_PERFMON_WORK 5 /* work for pfm_handle_work() */
#define TIF_PERFMON_CTXSW 6 /* perfmon needs ctxsw calls */
@@ -109,7 +108,8 @@ static inline struct thread_info *current_thread_info(void)
#define TIF_EMULATE_STACK_STORE 16 /* Is an instruction emulation
for stack store? */
#define TIF_MEMDIE 17 /* is terminating due to OOM killer */
-#define TIF_NEED_RESCHED_LAZY 18 /* lazy rescheduling necessary */
+#define TIF_POLLING_NRFLAG 18 /* true if poll_idle() is polling
+ TIF_NEED_RESCHED */
/* as above, but as bit values */
#define _TIF_SYSCALL_TRACE (1<<TIF_SYSCALL_TRACE)
next prev parent reply other threads:[~2013-08-02 14:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 11:24 [ANNOUNCE] 3.10.4-rt1 Thomas Gleixner
2013-08-01 11:34 ` Felipe Balbi
2013-08-02 0:03 ` Paul Gortmaker
2013-08-02 5:05 ` Benjamin Herrenschmidt
2013-08-02 12:45 ` Sebastian Andrzej Siewior
2013-08-02 14:19 ` Paul Gortmaker [this message]
2013-08-02 21:20 ` Benjamin Herrenschmidt
2013-08-12 8:14 ` Sebastian Andrzej Siewior
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=20130802141936.GA8267@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=benh@kernel.crashing.org \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).