Question on System Threads

NTDEV
1

Hello,

I create a system thread for my device and want it to be available at all
times.
I need it even when I receive the shutdown request - so that I can do some
post processing in this thread. Can I safely rely on this thread being
present at the time
when I receive the shutdown notification?

Is it correct to assume that since this thread is in the system process, it
should never
be killed (until I dont kill it explicitly)?

Thanks,
Gary.

2

My guess would be no. Where would the system process be executing from. If the driver is unloaded, the mapped region is freed ( or at least should be freed !

Waiting for an afermative answer !

Or it is possible that the driver would not be unloaded !!!

-pro

3

If my shutdown routine is called, this means that my driver is still in
memory.

Also, currently I am able to send request to my worker thread asking it to
do some flushing work
for me.

Thanks,
-Gary.

“Programmers Society Prokash Sinha” wrote in message
news:xxxxx@ntdev…
> My guess would be no. Where would the system process be executing from. If
the driver is unloaded, the mapped region is freed ( or at least should be
freed !
>
> Waiting for an afermative answer !
>
> Or it is possible that the driver would not be unloaded !!!
>
> -pro
>

4

You can perform your cleanup safely while you have the shutdown notification
request held incomplete in your driver. After that all bets are off. Your
thread will surely terminate at some point.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary
Sent: Thursday, November 18, 2004 7:05 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Question on System Threads

Hello,

I create a system thread for my device and want it to be
available at all times.
I need it even when I receive the shutdown request - so that
I can do some post processing in this thread. Can I safely
rely on this thread being present at the time when I receive
the shutdown notification?

Is it correct to assume that since this thread is in the
system process, it should never be killed (until I dont kill
it explicitly)?

Thanks,
Gary.

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as:
xxxxx@hollistech.com To unsubscribe send a blank email to
xxxxx@lists.osr.com

5

Cool. This is exactly what I am doing. In my shutdown routine, I wait
for the write request to be completed by my worker thread. After that,
I’ll never talk to the thread again.

Thanks a lot for the confirmation,
Gary

“Mark Roddy” wrote in message news:xxxxx@ntdev…
> You can perform your cleanup safely while you have the shutdown
notification
> request held incomplete in your driver. After that all bets are off. Your
> thread will surely terminate at some point.
>
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com] On Behalf Of Gary
> > Sent: Thursday, November 18, 2004 7:05 PM
> > To: Windows System Software Devs Interest List
> > Subject: [ntdev] Question on System Threads
> >
> > Hello,
> >
> > I create a system thread for my device and want it to be
> > available at all times.
> > I need it even when I receive the shutdown request - so that
> > I can do some post processing in this thread. Can I safely
> > rely on this thread being present at the time when I receive
> > the shutdown notification?
> >
> > Is it correct to assume that since this thread is in the
> > system process, it should never be killed (until I dont kill
> > it explicitly)?
> >
> > Thanks,
> > Gary.
> >
> >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> > http://www.osronline.com/article.cfm?id=256
> >
> > You are currently subscribed to ntdev as:
> > xxxxx@hollistech.com To unsubscribe send a blank email to
> > xxxxx@lists.osr.com
> >
>
>
>
>