Date: Wed, 31 Oct 2007 12:26:31 -0400 From: "Michael M. Press" <deathjestr@gmail.com> To: "=?ISO-8859-2?Q?Jaroszewski_=A3ukasz?=" <lukasz@salag.com>, Maslan <maslanbsd@gmail.com> Cc: freebsd-hackers@freebsd.org Subject: Re: ``Stopping RAM access'' Message-ID: <44b564930710310926m54f74566s104d12808ed5c9cb@mail.gmail.com> In-Reply-To: <319cceca0710301402j48355b54gc572f9c76a39d5a8@mail.gmail.com> References: <0862634D7E37134986CB15DF2E4542BA1C1EE5@sbssrv.SALAG.local> <319cceca0710301402j48355b54gc572f9c76a39d5a8@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> 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. > Also, keep in mind that 'cli/sti' is just a starting point. You can't just go playing with memory anywhere you want because interrupts are disabled. What if a DMA transfer is in progress? Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44b564930710310926m54f74566s104d12808ed5c9cb>