> > It appears to be making accesses to every page in a 32k block of data
> > allocated on the stack and every page in the current processes memory map.
> > One rationale for this might be to ensure that every page is in memory and
> > not paged out to disk, but it doesn't make sense on an embedded computer
> > with no swap disk. In addition, the line of code that actually makes the
> > memory access is missing from sbus.c but present in ts7500ctl.c. It goes
> > through all the motions of preparing to make all the memory accesses then
> > fails to do so.
> >
>
> I will check on this. This is incorrect if so.
>
It was incorrect -- thanks for the heads up. sbus.c has now been fixed on our
FTP site. I also just added an extra check to only follow mappings in
/proc/self/maps marked as readable. I ran across a system that mapped some
section of a library into the address space of the process as non-readable-- it
shouldn't attempt to cause a page fault in that case.
//Jesse Off
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|