Re: [2.6 patch] i386: always use 4k stacks

From: Giridhar Pemmasani (giri_at_lmc.cs.sunysb.edu)
Date: 11/14/05

  • Next message: Paul Jackson: "Re: [patch 3/5] atomic: atomic_inc_not_zero"
    Date:	Mon, 14 Nov 2005 17:14:39 -0500
    To: Alan Cox <alan@lxorguk.ukuu.org.uk>
    
    

    On Mon, 14 Nov 2005 22:33:57 +0000, Alan Cox <alan@lxorguk.ukuu.org.uk> said:

      Alan> Switch stack before calling the Windows bits. If we take an IRQ then
      Alan> the kernel will itself switch to its own IRQ stack for the IRQ
      Alan> handling. I don't think there is much more required.

    Shouldn't I have to prevent scheduler from changing the tasks when executing
    Windows code? Otherwise, kernel gets wrong current thread information,
    which is based on stack pointer. This is the stumbling block for implementing
    private stacks.

    Thanks,
    Giri
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/


  • Next message: Paul Jackson: "Re: [patch 3/5] atomic: atomic_inc_not_zero"

    Relevant Pages

    • Re: [patch, -rc5-mm1] locking validator: special rule: 8390.c disable_irq()
      ... btw I think this is no longer correct with the irq polling stuff Alan ... added to the kernel recently... ... We could make the misrouted IRQ logic skip all handlers on a disabled IRQ ...
      (Linux-Kernel)
    • [Full-disclosure] PHRACK 64: ATTACKING THE CORE
      ... - The Slab Allocator ... - Slab overflow exploiting: ... - Forcing a kernel path to sleep ... - Stack Frame Flow Recovery ...
      (Full-Disclosure)
    • Re: Interrupt context...
      ... > gone through most of the posts on interrupt in usenet. ... > kernel stack and ISR is executed. ... More may be saved depending on the architecture. ... Here the kernel have assembler code to save all general ...
      (comp.os.linux.development.system)
    • Re: Why is GForth-ITC fast?
      ... The kernel and the application code (so-called "userland") do not run ... That jump entails a "stack switch", ... the only thing is I guess if you want to do syscalls ...
      (comp.lang.forth)
    • Re: Kernel stack
      ... The problem is each process does not have a TSS of its own.Only one ... in another structure.A kernel stack of size 8k ... esp entry. ... This made me believe that the stack base is the ...
      (Linux-Kernel)