M5 Bugs

Login!
Register as a new userLost password?

for Project:

FS#326 — glibc reads /proc/meminfo and that can effect simulation

Attached to Project— M5 Bugs
Opened by Ali Saidi (saidi) - Monday, 08 December 2008, 05:12PM
Bug
Global/Other
New
No-one
All
High
Normal
2.0beta5
Undecided
Undecided
0%
The 20.parser benchmark tends to fail because glibc reads /proc/meminfo to determine how much memory is available in the system. qsort() uses that information to choose an algorithm to use thus depending on the host system, the guest can make a different choice. Ultimately, we need to provide a fake /proc/meminfo on open() syscalls that either has some generic info or better yet has the correct information for the simulated system.
This task depends upon

This task blocks these from closing