Hi there, I am asking a trivial question just in case I did not get it
right.
It is in my impression that, once a DpcForIsr is called and executed no
IOCTL function could interrupt the execution (LOWER IRQ).
Would I be though too carefull if I lock both DpcForIsr and IOCTL code that
access same data with a spinlock?
Thank you.
No aren’t being too careful, you need to do this for multi-processor
operation. With Hyper-threading and soon multi-core MP is becoming the
norm.
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
“Nikolas Stylianides” wrote in message news:xxxxx@ntdev…
> Hi there, I am asking a trivial question just in case I did not get it
> right.
>
> It is in my impression that, once a DpcForIsr is called and executed no
> IOCTL function could interrupt the execution (LOWER IRQ).
>
> Would I be though too carefull if I lock both DpcForIsr and IOCTL code
> that
> access same data with a spinlock?
>
>
>
> Thank you.
>
>
>
>
It isn’t that your dispatchand completion routines (IOCTL READ WRITE etc)
will interrupt your dpc routine, they won’t, it is that they can run
concurrent with your dpc routine.
=====================
Mark Roddy
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Nikolas Stylianides
Sent: Wednesday, March 02, 2005 10:26 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] [ntdev]DpcForIsr syncronization with IOCTLS
Hi there, I am asking a trivial question just in case I did not get it
right.
It is in my impression that, once a DpcForIsr is called and executed no
IOCTL function could interrupt the execution (LOWER IRQ).
Would I be though too carefull if I lock both DpcForIsr and IOCTL code that
access same data with a spinlock?
Thank you.
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
Yes, you are all right. Stupid of me I forgot that DpcForIsr could interrupt
an IOCTL routine. So that routine will never know that it was interrupted.
Thank you all.
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Roddy, Mark
Sent: Wednesday, March 02, 2005 5:40 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] [ntdev]DpcForIsr syncronization with IOCTLS
It isn’t that your dispatchand completion routines (IOCTL READ WRITE etc)
will interrupt your dpc routine, they won’t, it is that they can run
concurrent with your dpc routine.
=====================
Mark Roddy
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Nikolas Stylianides
Sent: Wednesday, March 02, 2005 10:26 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] [ntdev]DpcForIsr syncronization with IOCTLS
Hi there, I am asking a trivial question just in case I did not get it
right.
It is in my impression that, once a DpcForIsr is called and executed no
IOCTL function could interrupt the execution (LOWER IRQ).
Would I be though too carefull if I lock both DpcForIsr and IOCTL code that
access same data with a spinlock?
Thank you.
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com —
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@4plus.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Read what mark said. It is not a matter of “interrupting” or stopping the code operating in a process to process code in another. It is that in a MP or HT machine you can have your code running on multiple processors at the same time.
–
The personal opinion of
Gary G. Little
“Nikolas Stylianides” wrote in message news:xxxxx@ntdev…
Yes, you are all right. Stupid of me I forgot that DpcForIsr could interrupt an IOCTL routine. So that routine will never know that it was interrupted.
Thank you all.
------------------------------------------------------------------------------
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Roddy, Mark
Sent: Wednesday, March 02, 2005 5:40 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] [ntdev]DpcForIsr syncronization with IOCTLS
It isn’t that your dispatchand completion routines (IOCTL READ WRITE etc) will interrupt your dpc routine, they won’t, it is that they can run concurrent with your dpc routine.
=====================
Mark Roddy
------------------------------------------------------------------------------
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Nikolas Stylianides
Sent: Wednesday, March 02, 2005 10:26 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] [ntdev]DpcForIsr syncronization with IOCTLS
Hi there, I am asking a trivial question just in case I did not get it right.
It is in my impression that, once a DpcForIsr is called and executed no IOCTL function could interrupt the execution (LOWER IRQ).
Would I be though too carefull if I lock both DpcForIsr and IOCTL code that access same data with a spinlock?
Thank you.
—
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com —
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@4plus.com
To unsubscribe send a blank email to xxxxx@lists.osr.com