Since state information coming from Dom0 can arrive at any time, on
any CPU, we ought to make sure that a new state is fully initialized
before the target CPU might be using it.
Once touching that code, also do minor cleanup: A missing (but benign)
"break" and some white space adjustments.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Liu Jinsong <jinsong.liu@intel.com>
acpi_power->cpu, xen_cx->type);
return;
}
- cx = &acpi_power->states[acpi_power->count++];
+ cx = &acpi_power->states[acpi_power->count];
cx->type = xen_cx->type;
break;
}
break;
default:
cx->entry_method = ACPI_CSTATE_EM_NONE;
+ break;
}
- cx->latency = xen_cx->latency;
-
+ cx->latency = xen_cx->latency;
cx->target_residency = cx->latency * latency_factor;
+
+ smp_wmb();
+ acpi_power->count++;
if ( cx->type == ACPI_STATE_C1 || cx->type == ACPI_STATE_C2 )
acpi_power->safe_state = cx;
}