Re: WinXPSP2, Intel Core2Duo, Kernel drivers


<soviet_bloke@xxxxxxxxxxx> wrote in message
Well, you can think of my examples as of ones of the bugs if you wish -
no matter how you call them, these are the examples of doing something
you are not supposed to do, which may have undesirable effects (unless
you are 100% sure you know what you are doing)

Yes they are doing something you are not supposed to do, that is a pretty
good definition of a bug. For instance, if you forget that a routine uses
spinlocks and then accidently call it from your ISR, it may very well work
on an SMP system because the spinlock is an actual test and set, but it has
terrible consequences on a UP system where it becomes a NOP since the IRQL
is above DISPATCH_LEVEL.



--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
http://www.windrvr.com
Remove StopSpam from the email to reply



.

Relevant Pages

  • Re: WinXPSP2, Intel Core2Duo, Kernel drivers
    ... on an SMP system because the spinlock is an actual test and set, ... Trying to call the routine that uses spinlocks from ISR is not going to ... the very first step KeAcquireSpinLock() does is ...
    (microsoft.public.development.device.drivers)
  • Re: SpinLocks at DISPATCH_LEVEL
    ... Yes, you still need spinlocks. ... a spinlock is just raising IRQL to DISPATCH_LEVEL, ... Don Burn (MVP, Windows DDK) ... Remove StopSpam from the email to reply "Sam Fisher" wrote in message ...
    (microsoft.public.development.device.drivers)
Loading