* [ECOS] i386 memory questions
@ 2010-11-29 17:34 David Brennan
0 siblings, 0 replies; only message in thread
From: David Brennan @ 2010-11-29 17:34 UTC (permalink / raw)
To: eCos Disuss
Hello,
Is there an easy way within the current eCos infrastructure to
disallow certain memory access? I recently completed a project using a
different real-time operating system that had a guard page set up for
page 0. Then any null pointer dereferencing caused a page fault. This
turned out to be incredibly useful (especially since the page fault
trapped to the debugger).
As far as I can read the start up files, eCos does not use the MMU
(which is the way the other OS implemented this). Can the GDT be
configured to do this same thing? If so, does that break the 1:1
correlation between physical address and logical address?
If this is not possible with the GDT, would it be "easy" to set up the
MMU on an i386 platform? I really don't know anything about that level
of hardware/software configuration. Is there a recommended
architecture to use as a model for implementing it in proper eCos
style?
I am not looking to set up various protection levels. I would just
like to catch programming mistakes.
Thank you
David Brennan
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2010-11-29 17:34 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-11-29 17:34 [ECOS] i386 memory questions David Brennan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).