Re: [PATCH 22/25] x86/mcheck: Do the init in one place

From: Borislav Petkov
Date: Wed Nov 09 2016 - 12:01:17 EST


On Wed, Nov 09, 2016 at 05:24:51PM +0100, Sebastian Andrzej Siewior wrote:
> The behaviour was not changed - it was only reorganized to keep in one
> spot.

So there's the full CPU init path down cpu_up() -> ... -> identify_cpu()
where mcheck_cpu_init() is called and then there's also the hotplug
callbacks in mce_cpu_callback().

What you're proposing now is, merge the two.

But then the full path down identify_cpu() could still do
mheck_cpu_init() regardless where you move it.

IOW, I still don't see why this change is needed.

In more OW, why can't you simply do:

err = cpuhp_setup_state(CPUHP_AP_X86_MCE_STARTING, "x86/mce:starting",
mce_reenable_cpu, NULL);

and use the current notifier callback?

I still don't get the need for this churn.

--
Regards/Gruss,
Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.