lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 26 May 2010 22:42:28 -0400 From: Len Brown <lenb@...nel.org> To: x86@...nel.org, linux-pm@...ts.linux-foundation.org Cc: linux-kernel@...r.kernel.org, Len Brown <len.brown@...el.com> Subject: [PATCH 5/8] sched: clarify commment for TS_POLLING From: Len Brown <len.brown@...el.com> TS_POLLING set tells the scheduler a task will poll need_resched() to look for work. TS_POLLING clear tells resched_task() and wake_up_idle_cpu() that the remote CPU is sleeping in idle, and thus requires a reschedule interrupt to wake them to notice work. Update the description of TS_POLLING to reflect how it works. "cleared when sleeping in idle, requiring reschedule interrupt" Signed-off-by: Len Brown <len.brown@...el.com> Acked-by: Peter Zijlstra <peterz@...radead.org> --- arch/x86/include/asm/thread_info.h | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/x86/include/asm/thread_info.h b/arch/x86/include/asm/thread_info.h index e0d2890..0a14da2 100644 --- a/arch/x86/include/asm/thread_info.h +++ b/arch/x86/include/asm/thread_info.h @@ -241,8 +241,8 @@ static inline struct thread_info *current_thread_info(void) #define TS_USEDFPU 0x0001 /* FPU was used by this task this quantum (SMP) */ #define TS_COMPAT 0x0002 /* 32bit syscall active (64BIT)*/ -#define TS_POLLING 0x0004 /* true if in idle loop - and not sleeping */ +#define TS_POLLING 0x0004 /* clear when sleeping in idle + requiring reschedule interrupt */ #define TS_RESTORE_SIGMASK 0x0008 /* restore signal mask in do_signal() */ #define TS_XSAVE 0x0010 /* Use xsave/xrstor */ -- 1.6.0.6 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists