[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1411633925-9018-3-git-send-email-tianyu.lan@intel.com>
Date: Thu, 25 Sep 2014 16:32:04 +0800
From: Lan Tianyu <tianyu.lan@...el.com>
To: peterz@...radead.org, mingo@...nel.org, rafael.j.wysocki@...el.com,
srivatsa.bhat@...ux.vnet.ibm.com, toshi.kani@...com,
tianyu.lan@...el.com, ego@...ux.vnet.ibm.com, ktkhai@...allels.com,
laijs@...fujitsu.com, todd.e.brandt@...ux.intel.com,
srivatsa@....edu, fabf@...net.be, viresh.kumar@...aro.org
Cc: akpm@...ux-foundation.org, tipbot@...or.com,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org
Subject: [RFC PATCH V2 2/3] X86/CPU: Initialize MTRR/PAT when each cpu is online during system resume.
SDM Vol 3a section titled "MTRR considerations in MP systems" specifies
the need for synchronizing the logical cpu's while initializing/updating
MTRR.
Commit d0af9eed5a(x86, pat/mtrr: Rendezvous all the cpus for MTRR/PAT init)
delay the MTRR/PAT init for APs till all the logical cpu's come online and
the rendezvous process at the end of AP's bringup, will initialize the MTRR/PAT
for all AP's during boot and resume.
Currently, APs enabling are paralleled with resume devices during system resume
and the AP will be assigned with task before all APs' bringup. MTRR/PAT should
be initialized before running tasks. So this patch is to remove
set_mtrr_aps_delayed_init() for system resume and do the MTRR/PAT init when
the AP comes online just like dynamic single cpu online.
Signed-off-by: Lan Tianyu <tianyu.lan@...el.com>
---
kernel/cpu.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/kernel/cpu.c b/kernel/cpu.c
index 24c4889..30ffdd9 100644
--- a/kernel/cpu.c
+++ b/kernel/cpu.c
@@ -592,13 +592,10 @@ static int async_enable_nonboot_cpus(void *data)
{
int cpu;
- arch_enable_nonboot_cpus_begin();
-
for_each_cpu(cpu, frozen_cpus) {
_cpu_up_for_pm(cpu);
}
- arch_enable_nonboot_cpus_end();
cpumask_clear(frozen_cpus);
cpu_maps_update_done();
return 0;
--
1.8.4.rc0.1.g8f6a3e5.dirty
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists