On 12.09.2017 16:03, David Hildenbrand wrote:
> On 12.09.2017 15:43, Igor Mammedov wrote:
>> On Mon, 11 Sep 2017 17:21:47 +0200
>> David Hildenbrand wrote:
>>
>>> CPU hotplug is only possible on a per core basis on s390x.
>>>
>>> As we now have ms->possible_cpus, we can get rid
On 12.09.2017 15:43, Igor Mammedov wrote:
> On Mon, 11 Sep 2017 17:21:47 +0200
> David Hildenbrand wrote:
>
>> CPU hotplug is only possible on a per core basis on s390x.
>>
>> As we now have ms->possible_cpus, we can get rid of the global variable
>> cpu_states.
>>
>> While
On Mon, 11 Sep 2017 17:21:47 +0200
David Hildenbrand wrote:
> CPU hotplug is only possible on a per core basis on s390x.
>
> As we now have ms->possible_cpus, we can get rid of the global variable
> cpu_states.
>
> While rewriting s390_cpu_addr2state() completely to be based
CPU hotplug is only possible on a per core basis on s390x.
As we now have ms->possible_cpus, we can get rid of the global variable
cpu_states.
While rewriting s390_cpu_addr2state() completely to be based on
possible_cpus, move it to cpu.c, as it is independent of the virtio-ccw
machine.