Hello.
Wessel, Jason wrote:
> Sergei,
> If you are running with this patch you sent, this is why are you having
> problems with the swapper task getting killed on the x86_64.
> kgdb_unset_may_fault() is responsible for restoring the preempt count.
> And if it is not in the return path from a set_longjmp, then there is no
> way to restore the preempt count.
> It may seem counter intuitive to have the mayfault setup before
> settingup up the stack for a possible return from a long jump, but that
> is the way it works right now.
But... do we need to restore preempt_count on a "normal" exit path from
the functions making use of kgdb_fault_setjmp()? I guess not...
> Another possibility would be to split the functions to explicitly save
> the preempt count separately if you realy want to move the may_fault
> sets and unsets around.
Yeah, wrapping kgdb_fault_setjmp() into the code saving/restoreing preempt
count seems a way to go...
> Jason.
WBR, Sergei
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Kgdb-bugreport mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
