Ok. Just to make the discussion more concrete, the tables, which are not
all implemented, would be for SMBios/DMI, ACPI/APM, the Intel MP tables,
and the info gdb gathers using the BIOS to pass to the operating system
which includes the e820 table. There may be one or two I'm forgetting or
not aware of.
Gabe
Ali Saidi wrote:
I think Nate will have to say if Nested namespaces will work for
SimObjects. Perhaps a namespace like x86pc or something would be good
for the tables. I'm pretty sure most of that stuff is x86 only.
Ali
On Jun 2, 2008, at 9:53 PM, Gabe Black wrote:
This stuff is standardized for PCs but it might be useful for other
platforms as well. I'm not familiar enough with this stuff to really
be able to tell for sure, but if I had to guess I'd say it's not. I
was thinking of putting it in X86ISA and then into a nested BIOS
namespace.
Gabe
Ali Saidi wrote:
Take a look at how the Alpha TLB is done for how to make
SimObjects/Python happy with namespaces. The Params builder function
needs to be in the global name space.
One question is should it go in the x86 name space or in something
else?
Ali
On Jun 2, 2008, at 9:32 PM, Gabe Black wrote:
I'm just starting on making the BIOSey tables and configuration
information, like the e820 map which was forcing there to be 4 gigs
of memory, available through SimObjects. There are a bunch of
hierarchical tables for, for example, the DMI information, and I'm
concerned that if I add a bunch, maybe a few dozen, new names, I'll
end up either colliding with things that exist or making collisions
more likely later on. The obvious C++ answer to that would be a
namespace, but I'm not sure the best way to do that in this
circumstance. Regularly I think the python modules idea is supposed
to take care of this, but I'm not sure how that fits with our stuff
and some of the fancy voodoo we've got making it all work. I'm
going to try it that way and just see how it pans out, but if
anyone has any input I'd like to hear it.
Gabe
_______________________________________________
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev
_______________________________________________
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev
_______________________________________________
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev
_______________________________________________
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev
_______________________________________________
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev
