Vitaly Kuznetsov writes:
> Some time ago we forbade CPU offlining for Hyper-V and this was sufficient
> if you boot with all CPUs onlined. Turns out, people may want to limit the
> number online CPUs by passing 'maxcpus=' kernel parameter and we hit a
> crash in Hyper-V code in this case. After s
>
>> Subject: Re: [PATCH 0/7] hv: CPU onlining/offlining fixes and improvements
>>
>> On Fri, 25 Nov 2016 13:48:36 +0100
>> Vitaly Kuznetsov wrote:
>>
>> > Some time ago we forbade CPU offlining for Hyper-V and this was sufficient
>> > if you bo
> From: Stephen Hemminger [mailto:step...@networkplumber.org]
> Sent: Sunday, November 27, 2016 01:06
> To: Vitaly Kuznetsov
> Cc: de...@linuxdriverproject.org; linux-ker...@vger.kernel.org; KY Srinivasan
> ; Haiyang Zhang ; Dexuan Cui
>
> Subject: Re: [PATCH 0/7] hv: C
On Fri, 25 Nov 2016 13:48:36 +0100
Vitaly Kuznetsov wrote:
> Some time ago we forbade CPU offlining for Hyper-V and this was sufficient
> if you boot with all CPUs onlined. Turns out, people may want to limit the
> number online CPUs by passing 'maxcpus=' kernel parameter and we hit a
> crash in
Some time ago we forbade CPU offlining for Hyper-V and this was sufficient
if you boot with all CPUs onlined. Turns out, people may want to limit the
number online CPUs by passing 'maxcpus=' kernel parameter and we hit a
crash in Hyper-V code in this case. After some thinking, I think we may not
on
