Re: RFC: i386: kill !4KSTACKS
From: Mark Lord (lkml_at_rtr.ca)
Date: 09/07/05
- Previous message: Jeff Garzik: "Re: Patch for link detection for R8169"
- In reply to: Daniel Phillips: "Re: RFC: i386: kill !4KSTACKS"
- Next in thread: Lee Revell: "Re: RFC: i386: kill !4KSTACKS"
- Reply: Lee Revell: "Re: RFC: i386: kill !4KSTACKS"
- Reply: Daniel Phillips: "Re: RFC: i386: kill !4KSTACKS"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 06 Sep 2005 21:59:22 -0400 To: Daniel Phillips <phillips@istop.com>
Daniel Phillips wrote:
> There are only two stacks involved, the normal kernel stack and your new ndis
> stack. You save ESP of the kernel stack at the base of the ndis stack. When
> the Windows code calls your api, you get the ndis ESP, load the kernel ESP
> from the base of the ndis stack, push the ndis ESP so you can get back to the
> ndis code later, and continue on your merry way.
With CONFIG_PREEMPT, this will still cause trouble due to lack
of "current" task info on the NDIS stack.
One option is to copy (duplicate) the bottom-of-stack info when
switching to the NDIS stack.
Another option is to stick a Mutex around any use of the NDIS stack
when calling into the foreign driver (might be done like this already??),
which will prevent PREEMPTion during the call.
Cheers
-
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/
- Previous message: Jeff Garzik: "Re: Patch for link detection for R8169"
- In reply to: Daniel Phillips: "Re: RFC: i386: kill !4KSTACKS"
- Next in thread: Lee Revell: "Re: RFC: i386: kill !4KSTACKS"
- Reply: Lee Revell: "Re: RFC: i386: kill !4KSTACKS"
- Reply: Daniel Phillips: "Re: RFC: i386: kill !4KSTACKS"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|