Re: interrupt routine and application pages



"RJ" <RJ@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:C60CC328-2272-45D7-9611-DC859F738C1F@xxxxxxxxxxxxxxxx
Hello,
I have a requirement to examine currently running application stack on an
interrupt routine. Is it safe to read application memory on an interrupt
routine? What is IRQL at which page swapping happens? What is the mechanism
that can be used to make sure that memory area is safe to read?

I would like to use "MmProbeAndLockPages", but it can be used only <=
APC_LEVEL


Speaking of requirements... hmm... you don't have to do this in
the ISR at DIRQL. A DPC allows much more and is suitable for the task,
because the app won't have chance to run before the DPC exits.
Also, consider that the app and the ISR can run on different CPUs.

--PA


.



Relevant Pages

  • Re: help
    ... I had a Blue Screen Memory Dump and from that point on, ... F8, or Safe made. ... I also lost a 512MB DIMM RAM memory chip that does not even show ... when started it only boots for a moment ...
    (microsoft.public.windowsxp.general)
  • Re: Question about get-selections
    ... Is yours really what you use, or something typed from memory? ... ~M - select all automatically installed packages ... it was a safe place to leave such information. ... unnecessary files across the entire filesystem, ...
    (Debian-User)
  • Re: PC freezes
    ... I have run a AV scan in safe ... if the virtual memory could ... then the system could stall. ... Database Developer ...
    (microsoft.public.windowsxp.general)
  • Re: An RTOS without Memory Managment
    ... permit dynamic memory allocation at all so these buffers are provided statically by the application. ... the application safe is crazy talk. ... buffer is available for the next allocation. ...
    (comp.arch.embedded)
  • Re: Small ARM7 with realtime debug memory access?
    ... they all need an interrupt routine to send ... and display or even modify memory. ... routine to send information to the host". ... Certainly they let me also write to the target memory, ...
    (comp.arch.embedded)