Date: | Fri, 28 May 2010 05:56:24 -0600 |
---|---|
From: | Dan Gibson <degibson@xxxxxxxx> |
Subject: | Re: [Gems-users] Different execution instruction numbers between simics and opal |
1. To understand why you will see different instruction counts with different timings (e.g., different random seeds or different processor models), read Alameldeen and Wood, "Addressing Workload Variability in Architectural Simulations". PDF: http://www.cs.wisc.edu/multifacet/papers/ieeemicro03_variability.pdf
2. I don't think FFT binds itself at all by default, so disabling P2 and P3 might disable FFT threads. 3. Do not simply disable CPUs once the system is booted. The OS believes disabled CPUs are still running, and will still involve them in inter-processor interrupts (IPIs), e.g., TLB shootdowns. Disabling even one CPU will fairly rapidly deadlock the system, as the disabled CPU will not respond to IPIs and the system will eventually hang.
4. Not advancing a CPU in Opal is essentially the same as disabling it, so point #3 applies again. Regards, Dan On Fri, May 28, 2010 at 4:24 AM, shanshuchang <shanshuchang@xxxxxxxxx> wrote:
-- http://www.cs.wisc.edu/~gibson [esc]:wq! |
[← Prev in Thread] | Current Thread | [Next in Thread→] |
---|---|---|
|
Previous by Date: | [Gems-users] Different execution instruction numbers between simics and opal, shanshuchang |
---|---|
Next by Date: | Re: [Gems-users] Different execution instruction numbers between simics and opal, shanshuchang |
Previous by Thread: | [Gems-users] Different execution instruction numbers between simics and opal, shanshuchang |
Next by Thread: | Re: [Gems-users] Different execution instruction numbers between simics and opal, shanshuchang |
Indexes: | [Date] [Thread] |