delta/syslinux.git/core/thread, branch multifs git.kernel.org: pub/scm/boot/syslinux/syslinux.git debug: Adding -DDEBUG_THREAD 2015-09-04T15:57:52+00:00 Erwan Velu erwanaliasr1@gmail.com 2015-08-19T05:07:25+00:00 74b6a2777e6351edc85aac21a69dd51be5e1e9aa When debugging some syslinux code with debugging enabled, the threading code is so verbose that it completly slow down syslinux but also is so verbose that any other trace is invisible in the flood. This commit aims at requesting people to explicitly enable the threading logs by using -DDEBUG_THREAD. 
When debugging some syslinux code with debugging enabled, the threading
code is so verbose that it completly slow down syslinux but also is so
verbose that any other trace is invisible in the flood.

This commit aims at requesting people to explicitly enable the
threading logs by using -DDEBUG_THREAD.
core: make mbox_post()/__sem_down_slow() check if valid 2013-08-03T20:01:28+00:00 Gene Cumm gene.cumm@gmail.com 2013-08-03T20:01:28+00:00 ceb14335790f70378dddfbf0202d2bcda0c54a03 If the mailbox/semaphore is invalid, disallow additions. Signed-off-by: Gene Cumm <gene.cumm@gmail.com> 
If the mailbox/semaphore is invalid, disallow additions.

Signed-off-by: Gene Cumm <gene.cumm@gmail.com>
core: mbox/semaphore NULL checks 2013-08-03T19:59:26+00:00 Gene Cumm gene.cumm@gmail.com 2013-08-03T19:59:26+00:00 dc3059be195f0b1c878273f648dcaf1b45c5a860 Also set mbox invalid and mbox pointer NULL when free()d Signed-off-by: Gene Cumm <gene.cumm@gmail.com> 
Also set mbox invalid and mbox pointer NULL when free()d

Signed-off-by: Gene Cumm <gene.cumm@gmail.com>
pxe: always start the idle thread, in case we need it 2012-05-30T02:33:20+00:00 H. Peter Anvin hpa@zytor.com 2012-05-30T02:33:20+00:00 7699e996c613e51049e0bad6ade32215ac263289 Always start the idle thread, but leave it blocked unless we have an indication that interrupts are not working. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
Always start the idle thread, but leave it blocked unless we have an
indication that interrupts are not working.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
thread: Add magic number, debugging code, min stack size 2012-03-30T23:13:02+00:00 H. Peter Anvin hpa@zytor.com 2012-03-30T23:09:03+00:00 12b2033fc541241f1b5a286a1a80dd309fe2a708 Add a magic number to the thread control block; this helps check for memory overwrites. Add dprintf()s to the scheduler. Force a minimum stack size. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
Add a magic number to the thread control block; this helps check for
memory overwrites.

Add dprintf()s to the scheduler.

Force a minimum stack size.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
idle_thread: safer interrupt handling 2012-03-28T06:02:38+00:00 H. Peter Anvin hpa@zytor.com 2012-03-28T06:02:38+00:00 6b6d07cc4afdb8f1bf56f44f3fee6f02a590bb84 Make sure we use "sti ; hlt" to make sure we don't go to sleep when we suddenly have an interrupt coming in. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
Make sure we use "sti ; hlt" to make sure we don't go to sleep when we
suddenly have an interrupt coming in.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
thread: fix warnings 2011-05-02T01:05:23+00:00 H. Peter Anvin hpa@zytor.com 2011-05-02T01:05:23+00:00 f8e82f9f4dab637783b5dbcec61956bba1c57faf Fix set-but-not-used variable warnings and undefined references. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
Fix set-but-not-used variable warnings and undefined references.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
thread: simplify the scheduler 2011-04-30T19:21:57+00:00 H. Peter Anvin hpa@zytor.com 2011-04-30T19:21:57+00:00 da6d596aae0ebd3d4f6042ae361812242981a46e need_schedule was no longer used by anything else, and schedule_lock only verified if we were being called from inside sched_hook_func(). Make the localness of this data explicit. While we're at it, call kaboom if we ever find ourselves without a runnable thread (which should not be possible, as the idle thread is not allowed to block.) Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
need_schedule was no longer used by anything else, and schedule_lock
only verified if we were being called from inside sched_hook_func().
Make the localness of this data explicit.

While we're at it, call kaboom if we ever find ourselves without a
runnable thread (which should not be possible, as the idle thread is
not allowed to block.)

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
exit_thread: easier form of the same test... 2011-04-30T19:11:48+00:00 H. Peter Anvin hpa@zytor.com 2011-04-30T19:11:48+00:00 c69a11a0e4e232965845b8fa3e059f10e6715ef8 Instead of testing __schedule_lock explicitly, we can just call kaboom() if the scheduler returns, since that can only happen if the scheduler lock is set, and is in fact the reason we can't be here with the scheduler locked in the first place. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
Instead of testing __schedule_lock explicitly, we can just call
kaboom() if the scheduler returns, since that can only happen if the
scheduler lock is set, and is in fact the reason we can't be here with
the scheduler locked in the first place.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
exit_thread: make sure we don't run under scheduler lock 2011-04-30T19:09:41+00:00 H. Peter Anvin hpa@zytor.com 2011-04-30T19:09:41+00:00 4db50faba162ad1c5803173ac562326934d016e1 If we ever end up in __exit_thread with the scheduler locked, we're completely fscked. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
If we ever end up in __exit_thread with the scheduler locked, we're
completely fscked.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>