Messages in this thread | | | Subject | Re: schedule() && prev/current (Was: [PATCH 3/3] Make get_current() __attribute__((const))) | From | Peter Zijlstra <> | Date | Wed, 19 May 2010 12:37:45 +0200 |
| |
On Wed, 2010-05-19 at 12:27 +0200, Oleg Nesterov wrote:
> Now suppose that A calls schedule() and we switch to B. When switch_to() > returns on B's context, this context (register/stack) matches the previous > context which was used by B when it in turn called schedule(), correct?
Ah, right, you always schedule back to where you came from,... I shouldn't try and write emails before the morning juice hits ;-)
| |