[lkml]   [2004]   [Sep]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: get_current is __pure__, maybe __const__ even
    On Wed, 2004-09-15 at 22:36, William Lee Irwin III wrote:
    >> Not over a call to schedule(). In the midst of schedule().

    On Wed, Sep 15, 2004 at 11:49:38PM -0400, Albert Cahalan wrote:
    > OK, let's look.
    > First, there's fork/vfork/clone. At no point does
    > "current" change. A process comes into existance
    > with a ready-made current.
    > Second, there's sched.c with context_switch().
    > That does everything via switch_to, like so:
    > /* Here we just switch the register state and the stack. */
    > switch_to(prev, next, prev);
    > No problem. Now I only need to show that switch_to()
    > is safe. Unfortunately, it's arch-specific code.
    > I'll look at a few examples...

    gcc has to compile more than Linux. There has to be a rule for how this
    works, not "gee, Linux will still work and get faster if we change this".

    -- wli
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 14:06    [W:0.020 / U:47.380 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site