* build/ALPHA/tests/opt/quick/se/60.rubytest/alpha/linux/rubytest-ruby
passed.
* build/ALPHA/tests/opt/quick/se/00.hello/alpha/linux/simple-atomic passed.
* build/ALPHA/tests/opt/quick/se/30.eio-mp/alpha/eio/simple-atomic-mp
passed.
*
On July 28, 2014, 12:34 a.m., Andreas Hansson wrote:
Thanks for the input Amin. One high-level question: what is the main aim of
the patch? Until now we have tried to keep the timing constraints to a
minimum (without sacrificing fidelity). In general you could argue that
tBURST can
On July 28, 2014, 12:34 a.m., Andreas Hansson wrote:
Thanks for the input Amin. One high-level question: what is the main aim of
the patch? Until now we have tried to keep the timing constraints to a
minimum (without sacrificing fidelity). In general you could argue that
tBURST can
On July 28, 2014, 12:34 a.m., Andreas Hansson wrote:
Thanks for the input Amin. One high-level question: what is the main aim of
the patch? Until now we have tried to keep the timing constraints to a
minimum (without sacrificing fidelity). In general you could argue that
tBURST can
On July 14, 2014, 4:42 p.m., Andreas Sandberg wrote:
I have two high-level comments that need to be fixed:
* This is should be four different commits (configuration, CPUID updates,
segment initialization, kvm, process).
* Write a proper commit message (see
