Re: [PATCH v2 0/2] Drivers: hv: vmbus: use cpu_hotplug_enable/disable for CPU offlining prevention

[Vitaly Kuznetsov]

KY Srinivasan <kys@xxxxxxxxxxxxx> writes:

>> -----Original Message-----
>> From: Vitaly Kuznetsov [mailto:vkuznets@xxxxxxxxxx]
>> Sent: Thursday, May 21, 2015 9:22 AM
>> To: devel@xxxxxxxxxxxxxxxxxxxxxx
>> Cc: KY Srinivasan; Haiyang Zhang; linux-kernel@xxxxxxxxxxxxxxx; Dexuan Cui;
>> Ingo Molnar; Paul E. McKenney; Rafael J. Wysocki; Peter Zijlstra; Thomas
>> Gleixner; Radim KrÄmÃÅ
>> Subject: [PATCH v2 0/2] Drivers: hv: vmbus: use cpu_hotplug_enable/disable
>> for CPU offlining prevention
>> 
>> Changes since v1:
>> - Make cpu_hotplug_disabled a counter [Radim KrÄmÃÅ]
>> 
>> Export cpu_hotplug_enable/cpu_hotplug_disable functions from cpu.c and
>> use
>> them instead of altering smp_ops.cpu_disable in Hyper-V vmbus module.
>> 
>> Vitaly Kuznetsov (2):
>>   cpu-hotplug: export cpu_hotplug_enable/cpu_hotplug_disable
>>   Drivers: hv: vmbus: use cpu_hotplug_enable/disable
>
> Vitaly,
>
> Since there is a cross tree dependency here, could you resubmit the vmbus patch
> after the CPU hotplug patch has been committed. 

I'm afraid it won't be committed without the second patch as without a
single user of cpu_hotplug_enable/cpu_hotplug_disable (among modules)
this patch doesn't make much sense. I would rather expect both of them
to go through Greg's tree but with proper sign-offs/reviewed-bys. And
of course this decision is up to tree maintainers, I'll resubmit the
vmbus patch in case CPU hotplug patch gets committed separately.

Thanks,

>
> Regards, 
>
> K. Y
>> 
>>  Documentation/power/suspend-and-cpuhotplug.txt |  6 ++--
>>  drivers/hv/vmbus_drv.c                         | 38 +++-----------------------
>>  kernel/cpu.c                                   | 13 +++++----
>>  3 files changed, 15 insertions(+), 42 deletions(-)
>> 
>> --
>> 1.9.3

-- 
  Vitaly
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/