Re: kernel/sched.c questions

[Andi Kleen <ak@suse.de>]

Tim Walberg <tewalberg@mediaone.net> writes:

> On 04/04/2001 16:52 -0300, Sardañons, Eliel wrote:
> >>	Hello, I would like to know why you put this two functions:
> >>	void scheduling_functions_start_here(void) { }
> >>	...
> >>	void scheduling_functions_end_here(void) { }
> >>	
> 
> That one I have no idea about - maybe some perverse sort
> of comment? Or maybe something somewhere needs to know the
> address range that some functions lie within, and these functions
> would delimit that range. Of course, that presumes that the
> compiler in use doesn't reorder functions in the object code
> that emits, but I think that's a fairly safe assumption for
> now...

This is needed for a very bad hack to get the EIP information in ps -lax:
most programs would be shown as hanging in schedule(), which would not be 
very useful to show the user. To avoid this sched.c is always compiled with 
frame pointers and if the EIP is inside these two functions the proc code 
goes back one level in the stack frame.


-Andi