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

On Mon, 14 Nov 2005 22:33:57 +0000, Alan Cox <[email protected]> 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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Re: [2.6 patch] i386: always use 4k stacks
    • From: Alex Davis <[email protected]>
  • Re: [2.6 patch] i386: always use 4k stacks
    • From: Alan Cox <[email protected]>
  • Re: [2.6 patch] i386: always use 4k stacks
    • From: Giridhar Pemmasani <[email protected]>
  • Re: [2.6 patch] i386: always use 4k stacks
    • From: Alan Cox <[email protected]>

• Prev by Date: Re: More cleanups for sharpsl_pm.c
• Next by Date: [RFC] EDAC and the sysfs
• Previous by thread: Re: [2.6 patch] i386: always use 4k stacks
• Next by thread: Re: [2.6 patch] i386: always use 4k stacks
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]