nathan binkert wrote:
The reason I'd want to enumerate children is so I can find any memory
objects below the CPU and determine what available ranges I can add into
the map. If there ends up being in-memory-system address transformation
in the future that could be more complicated, but for
For now though, I'd say that you should probably just have whatever
SimObject that represents BIOS data just get a pointer to a list of
memobjects.
How would I get that list? Would I do that in C++ or in the python?
Either is fine with me but I'm not clear on how that would work.
I'm back in Ann Arbor waiting for my brother's surgery and I haven't had
a chance to go back and get my desktop to work from, so I'm fiddling
around with trying to get this to work. What I'm thinking to do is
basically to just make the places I stick BIOS tables reserved and
everything else up to
I'm not clear on exactly what you're doing here. Why is the area
reserved? Are you talking about physical memory on the host? Why do
you need to enumerate children? Details...
Nate
On Sat, May 3, 2008 at 8:27 AM, Gabe Black [EMAIL PROTECTED] wrote:
I'm back in Ann Arbor waiting for my
Basically, the e820 map is to tell the OS what areas of memory it can
use and what areas hold the BIOS itself and the data tables it needs to
operate. There are some areas in higher addresses which I'm not sure
what they're for, but I suspect it's something to do with PCI devices or
bridges or
The reason I'd want to enumerate children is so I can find any memory
objects below the CPU and determine what available ranges I can add into
the map. If there ends up being in-memory-system address transformation
in the future that could be more complicated, but for now just getting a
There's also a kernel command line option to override the bios notion
of how much ram there is. Did you try that? No matter what you do,
you must come up with a way to make the amount of memory configurable.
On Sat, Apr 26, 2008 at 10:00 PM, Gabe Black [EMAIL PROTECTED] wrote:
Well, it's not
I agree. This is something I plan to do once I get, for instance, a bash
shell working just so I can have a mostly known working entity to start
from and to cut down on where problems could be from. I'm going to have
to spend some time in Edwardsburg (my parent's house) because of a
family
Is it too difficult to track down which piece of BIOS info you copied
contains the DRAM size, or copy the info from a machine with less RAM?
In the long run we'll want to make it configurable, and clearly in
the real world it's OK to have a PC with 4GB of RAM...
On Sat, Apr 26, 2008 at 3:46 PM,
We talked about doing precisely that several years ago. You can also
then compress the individual pages and also hash them so that you only
need one copy of any page that's replicated. There is a probably a
flyspray task to do just that, but no one got around to doing it. In
the short term
10 matches
Mail list logo
