Hi D,
I don’t know much about the Page Fault Handlers other than the various
algorithms used my the Memory Manager to swap a page into the memory from
the disk.Why is it that, the Page Fault is not allowed at Dispatch Level
?..What I understand from a Page Fault is that the driver routine trying to
access a page is right now not there in the memory and should be swapped
in…Who/When actually generates a Page Fault and who/how is it handled
?..I know this might seem to be a basic question,but I am not very much
clear with this…
Thanks.
Best Regards,
Sai Prasad
**************************************************************************
This email (including any attachments) is intended for the sole use of the
intended recipient/s and may contain material that is CONFIDENTIAL AND
PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or
distribution or forwarding of any or all of the contents in this message is
STRICTLY PROHIBITED. If you are not the intended recipient, please contact
the sender by email and delete all copies; your cooperation in this regard
is appreciated.
**************************************************************************
> the disk.Why is it that, the Page Fault is not allowed at Dispatch
Level
?
Resolving a page fault can require wait for inpage IO operation to
complete. Waits on DISPATCH_LEVEL are not allowed.
Max
I would highly recommend you pick up a good book on kernel mode driver
developing for NT based OSes. For the type of questions you are asking the
book by Viscarola and Mason is probably the best reference you could buy.
It is an NT4 driver based book, but pretty much all they discuss is still
relevant. From this book you will get a lot of info about IRQLs, the
scheduler, dispatch objects, the memory manager, I/O, interrupts, most of
the basic OS operation and driver operation fundamentals.
For a good book on WDM drivers I would recommend the book by Oney.
Excellent coverage of PnP and Power, queues, lots of good stuff.
Oh, and the Inside 2000 book by Russinovich and Solomon is an excellent
source of info on the OS as well, especially the memory manager.
These are the best three books out there IMHO. These are the only three
books I really ever reference as well, but that is me. Anyway, I think this
would go a long way to answering your questions in a more comprehensive
manner.
–
Bill McKenzie
“Sai_Prasad” wrote in message news:xxxxx@ntdev…
>
> Hi D,
> I don’t know much about the Page Fault Handlers other than the various
> algorithms used my the Memory Manager to swap a page into the memory from
> the disk.Why is it that, the Page Fault is not allowed at Dispatch Level
> ?..What I understand from a Page Fault is that the driver routine trying
to
> access a page is right now not there in the memory and should be swapped
> in…Who/When actually generates a Page Fault and who/how is it handled
> ?..I know this might seem to be a basic question,but I am not very much
> clear with this…
>
> Thanks.
> Best Regards,
> Sai Prasad
>
>
> This email (including any attachments) is intended for the sole use of the
> intended recipient/s and may contain material that is CONFIDENTIAL AND
> PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying
or
> distribution or forwarding of any or all of the contents in this message
is
> STRICTLY PROHIBITED. If you are not the intended recipient, please contact
> the sender by email and delete all copies; your cooperation in this regard
> is appreciated.
>
>
>
Hi Bill,
Thanks.
Regs,
Sai
~ If u r not living on the edge, u r occupying too much of space ~
Keep 
From: Bill McKenzie[SMTP:xxxxx@driver.attbbs.com]
Reply To: NT Developers Interest List
Sent: Monday, June 24, 2002 7:27 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Page Fault Not Allowed at Dispatch Level ???
I would highly recommend you pick up a good book on kernel mode driver
developing for NT based OSes. For the type of questions you are asking
the
book by Viscarola and Mason is probably the best reference you could buy.
It is an NT4 driver based book, but pretty much all they discuss is still
relevant. From this book you will get a lot of info about IRQLs, the
scheduler, dispatch objects, the memory manager, I/O, interrupts, most of
the basic OS operation and driver operation fundamentals.
For a good book on WDM drivers I would recommend the book by Oney.
Excellent coverage of PnP and Power, queues, lots of good stuff.
Oh, and the Inside 2000 book by Russinovich and Solomon is an excellent
source of info on the OS as well, especially the memory manager.
These are the best three books out there IMHO. These are the only three
books I really ever reference as well, but that is me. Anyway, I think
this
would go a long way to answering your questions in a more comprehensive
manner.
–
Bill McKenzie
“Sai_Prasad” wrote in message news:xxxxx@ntdev…
> >
> > Hi D,
> > I don’t know much about the Page Fault Handlers other than the
> various
> > algorithms used my the Memory Manager to swap a page into the memory
> from
> > the disk.Why is it that, the Page Fault is not allowed at Dispatch Level
> > ?..What I understand from a Page Fault is that the driver routine
> trying
> to
> > access a page is right now not there in the memory and should be swapped
> > in…Who/When actually generates a Page Fault and who/how is it handled
> > ?..I know this might seem to be a basic question,but I am not very much
> > clear with this…
> >
> > Thanks.
> > Best Regards,
> > Sai Prasad
> >
> >
>
> > This email (including any attachments) is intended for the sole use of
> the
> > intended recipient/s and may contain material that is CONFIDENTIAL AND
> > PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying
> or
> > distribution or forwarding of any or all of the contents in this message
> is
> > STRICTLY PROHIBITED. If you are not the intended recipient, please
> contact
> > the sender by email and delete all copies; your cooperation in this
> regard
> > is appreciated.
> >
>
> >
> >
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@bla.satyam.com
> To unsubscribe send a blank email to %%email.unsub%%
>
This email (including any attachments) is intended for the sole use of the
intended recipient/s and may contain material that is CONFIDENTIAL AND
PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or
distribution or forwarding of any or all of the contents in this message is
STRICTLY PROHIBITED. If you are not the intended recipient, please contact
the sender by email and delete all copies; your cooperation in this regard
is appreciated.