* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/o3-timing passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing passed.
*
On Wed, May 21, 2008 at 5:44 PM, Gabe Black [EMAIL PROTECTED] wrote:
The kernel is now getting to a point where it's trying to calibrate the
timer in the local APIC against the TSC register. In order to mimic that,
I'm going to need to create an event to fire when the timer is supposed to
One problem is that this isn't a parent/child relationship. For
instance, there could be four CPUs and four local APICs all on the same
bus, and they need to know which one goes with which CPU. In that case
it would be arbitrary. If the interconnect isn't a bus, then you can't
just stick the
So anyway, now that we seem to have the current version in there,
what about the original question which was about the latest mainline
revision?
Ali Saidi wrote:
That wouldn't be ideal because we would need to emulate everything
Object() is doing to get the c compiler and options right.
As I said in an email earlier, you had pointed out that if somebody
sends in the output of m5, it's nice to be able to easily tell it's beta
4 or beta 3 or somewhere in the middle and they, for instance, might
need the cache patches without having to go back and forth teasing out
details. My
Well, I imagine most people will use mercurial at least to check out
the code in which case we'll have the last ID. Perhaps we want to
include the qbase revision as well incase lot of people use MQ.
Speaking of which when the repository is made available we probably
want a pretty good
