Re: ``Stopping RAM access''

Can anyone give me a clue, how one can ``stop'' system from accessing RAM, and then allow it again?

I think this has no aim, RAM tests should be done during booting, but
u could try to disable interrupts while in kernel mode 'cli' which
will prevent any further context switching, then try to do whatever
you want, finally enable interrupts back 'sti'.

That's my two cents. I don't whether it will work or not.


--
System Programmer
--
I'm Searching For Perfection,
So Even If U Need Portability U've To Use Assembly ;-)
--
http://libosdk.berlios.de
_______________________________________________
freebsd-hackers@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: CLI doubt
    ... > One can do a CLI to disable interrupts. ... does this instruction disable everything? ... Michael Brown ...
    (comp.lang.asm.x86)
  • [RESEND] [PATCH 1/7] ppc: remove cli()/sti() in arch/ppc/4xx_io/serial_sicc.c
    ... save_flags; cli(); ... /* disable interrupts while stopping serial port interrupts */ ... static void siccuart_flush_chars ...
    (Linux-Kernel)
  • Re: CLI doubt
    ... >> One can do a CLI to disable interrupts. ... you could look at an SMI ... but how would i actually programmatically cause an NMI? ...
    (comp.lang.asm.x86)
  • Re: CLI doubt
    ... >> One can do a CLI to disable interrupts. ... >> opcodes, load invalid segment selectors, and so on? ... Are INT ...
    (comp.lang.asm.x86)
  • CLI doubt
    ... excuse me for the totally newbie question... ... One can do a CLI to disable interrupts. ... opcodes, load invalid segment selectors, and so on? ...
    (comp.lang.asm.x86)