* 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.
*
Hi,
I am now trying to boot SPARC_FS with just one processor and in the attached
terminal I see:
cpu
ERROR: 1 CPUs in PD did not start
Could this be because of the patch I applied? Thank you.
The reason I want to boot SPARC_FS with one processor is because I want to
create a checkpoint. Is it
Ali,
Just to be sure, are you using T1 or T2 release of OpenSparc? Thanks.
Polina
Well, it's probably best to actually make 2 CPUs work and then go back
and fix things for N CPUs. It should be possible to make the
hypervisor description file (1g2p-hv.bin) understand that CPU 1 should
T1 The hv and md description files need to match the configuration
you're running. If you're only running 1 processor you need to change
the hv and md files to the 1up configuration (as opposed to the 1g2p
versions).
Ali
On Mar 3, 2009, at 9:10 PM, Polina wrote:
Ali,
Just to be
On Mar 3, 2009, at 9:48 PM, Polina wrote:
Hi Ali,
Thanks for your help. I hate to keep asking things, but there's little
documentation. I appreciate you taking the time to respond to my
emails.
Oh, I see now. Would I follow the procedure outline in OpenSPARC
readme
files for
With a few hacks that will need to be sorted out at some point, I've
pretty much got an SMP kernel booting. One problem I just diagnosed was
that the lock prefix is not honored, and amazingly, two atomic
operations manipulating the same lock lined up on top of each other
exactly. I think
* 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.
*
