On 04/08/2015 10:01 AM, Frederic Weisbecker wrote:
How about creating smpboot_update_mask_percpu_thread() and handle it from smpboot, this way future evolutions of smpboot won't overlook this cpumask live change?
It seemed like your proposed approach was actually a bit heavier-weight from the perspective of generic smp_hotplug_thread, so instead I just modified the proposed API to have a simple "valid_cpu()" callback, which I think is clear and won't be damaged by smpboot evolution. Let me know what you think. -- Chris Metcalf, EZChip Semiconductor http://www.ezchip.com -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
