On Thu, 2013-06-13 at 19:25 +0800, Zhao Chenhui wrote: > Some multicore SoCs firstly boot up the cpu0 after warm reset. > In some suspend/resume cases, SoC will do a warm reset when resuming. > In order to ensure that the suspending and resuming is running > on a same cpu, cpu0 should be the last cpu to suspend. Here, cpu0 is > the boot_cpuid.
Well, so: - In any case, your patch will break pseries, so it's not acceptable. - Why does it have to absolutely resume from the same CPU it suspended from ? Can't you have a little bit of code on the resuming CPU that checks if it's not online, poke an online one and goes back to sleep ? Cheers, Ben. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
