top: always validate that p-core/e-core identification
Prior to this commit, when the '5' key was struck, top would check for the presence of e-cores just one time. That meant if a some cpu was brought online, and it in turn exposed a new e-core after top has started, users needed a top restart to activate the new '5' feature. So, now we'll check for any e-cores with each '5' key. Signed-off-by: Jim Warner <james.warner@comcast.net>
This commit is contained in:
parent
f571746af2
commit
c7568b28fb
@ -5806,12 +5806,10 @@ static void keys_summary (int ch) {
|
||||
|| ((w->rc.combine_cpus))))
|
||||
show_msg(N_txt(XTRA_modebad_txt));
|
||||
else {
|
||||
static int scanned;
|
||||
if (!scanned) {
|
||||
for (; scanned < Cpu_cnt; scanned++)
|
||||
int scanned;
|
||||
for (scanned = 0; scanned < Cpu_cnt; scanned++)
|
||||
if (CPU_VAL(stat_COR_TYP, scanned) == E_CORE)
|
||||
break;
|
||||
}
|
||||
if (scanned < Cpu_cnt) {
|
||||
w->rc.core_types += 1;
|
||||
if (w->rc.core_types > E_CORES_ONLY)
|
||||
|
Loading…
Reference in New Issue
Block a user