[uml-devel] sched and stack patch changelogs.

[Allan Graves <allan.graves@oracle.com>]

BB: Sorry I hadn't included a changelog, Jeff and I had talked about this a lot, I forgot that other people would be reading them. :)  

Author: Allan Graves<allan.graves@gmail.com>
	Scheduler Cleanup Patch:
	This patch moves code that is in both switch_to_tt and switch_to_skas to the top level _switch_to function, keeping us from duplicating code.  It is required for the stack trace patch to work properly.

	Stack Trace Patch:
	This patch implements a stack trace for a thread, not unlike sysrq-t does.  The advantage to this is that a break point can be placed on showreqs, so that upon showing the stack, you jump immediately into the debugger.
	While sysrq-t does the same thing, sysrq-t shows *all* threads stacks.  It also doesn't work right now.  In the future, I thought it might be acceptable to make this show all pids stacks, but perhaps leaving well
	enough alone and just using sysrq-t would be okay.  For now, upon receiving the stack command, UML switches context to that thread, dumps its registers, and then switches context back to the original thread.  Since 
	UML compacts all threads into one of 4 host threads, this sort of mechanism could be expanded in the future to include other debugging helpers that sysrq does not cover.  



Blaisorblade wrote:

>On Friday 02 September 2005 18:59, Jeff Dike wrote:
>  
>
>>On Wed, Aug 31, 2005 at 07:06:33PM -0400, Allan Graves wrote:
>>    
>>
>>>Jeff,
>>>Here's the patches.  Hope these meet your approval!
>>>      
>>>
>Could you please write a proper changelog? Reading a patch is possible, but 
>needs time which I don't have in the very moment.
>
>Also, what is the difference between your "stack trace" patch, which adds a 
>member to thread_struct, for each process, so I'd like a minimum of 
>justification, and one of the sysrq options which does exactly this?
>
>Apart that the second is currently buggy, and is global, as in what you plan 
>here:
>
>/* Would be nice:
>+           1) Send showregs output to mconsole.
>+           2) Add a way to stack dump all pids.
>+        */
>
>Sorry if these questions seem bad - but that's why changelogs are used.
>  
>
>>>Allan
>>>      
>>>
>
>  
>


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel