* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-atomic-mp
passed.
* build/ALPHA_SE/tests/fast/quick/01.hello-2T-smt/alpha/linux/o3-timing
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing passed.
*
nathan binkert wrote:
Seems like it would be worth setting up a slew of g++ revs on zizzer
and running regressions under all of them, maybe on a rotating
basis...
Yeah, I agree. Multiple revs of swig and maybe scons would be good
too. I think we should set up a separate compile
Hello Gabe,
Thanks for the reply. I have used Simics for booting a disk image and
running workloads for the X86 architecture and I would like to try the
same on M5. I have a few questions regarding this.
1) Is M5 currently capable of doing this?
2) Is the X86 processor model cycle accurate?
3) If
That depends on what's on the disk image. If it's a 64 bit uniprocessor
Linux kernel, it will likely almost work, or possibly actually work. If
it's any other OS I don't know what will happen since I haven't tried it
myself. In M5, CPU models are not generally for one ISA or another.
Please don't do anything with the TLBs yet. I'm hoping to send out a
patch tonight.
Gabe
nathan binkert wrote:
1) Anybody have any problems if I remove the last remnants of
turbolaser code that's in the TLB? We haven't had the devices in
forever and I just don't see it ever being used?
2)
Please don't do anything with the TLBs yet. I'm hoping to send out a
patch tonight.
No problem.
___
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev
Patch subject is complete summary.
# HG changeset patch
# User Gabe Black gbl...@eecs.umich.edu
# Date 1236576344 25200
# Node ID 1c069851445b283974b8c1ed4102659ef86b96e4
# Parent 74bc713c71ce4e2a2e29958ff2f4c6f5c6ab6aa0
imported patch unifytlb.patch
diff --git a/src/arch/alpha/AlphaTLB.py
