current->need_reshed, can it be a global flag ?

instead of need_reshed being a per-task flag, could it be as a global flag ?, since every time current->need_reshed is checked, schedule() is just called to pick another process. --- ðÏÌÕÞÉÔÅ É ÷Ù Ó×ÏÊ ÂÅÓÐÌÁÔÎÙÊ ÜÌÅËÔÒÏÎÎÙÊ ÁÄÒÅÓ ÎÁ http://Mail.ru - To unsubscribe from this list: send the line

Re[2]: switch_to()/doesnt %esp get replaced with %ebp on ret

m switch_to and ran and it promptly crashed. But with -fomit-frame-pointer, all this does not take place. Still, could some one enlighten me on why esi and edi are also similarly saved and restored ? -Original Message- From: Jamie Lokier <[EMAIL PROTECTED]> To: Parity Error <[EMAIL

switch_to()/doesnt %esp get replaced with %ebp on ret

in schedule(), switch_to() macro changes esp to the new process's stack. But, on exit frm schedule, how come it does not get overwritten with ebp-24, as the dissasembled code shows. The code was compiled without the -fomit-frame-pointer. pushl 508(%ecx) jmp __switch_to 1: po