On 27/03/2019 17:29, Jan Beulich wrote:
>>>> On 18.03.19 at 14:11, <jgr...@suse.com> wrote:
>> --- a/xen/common/cpu.c
>> +++ b/xen/common/cpu.c
>> @@ -214,7 +214,12 @@ void enable_nonboot_cpus(void)
>> printk("Error bringing CPU%d up: %d\n", cpu, error);
>> BUG_ON(error == -EBUSY);
>> }
>> + else
>> + __cpumask_clear_cpu(cpu, &frozen_cpus);
>> }
>>
>> + for_each_cpu ( cpu, &frozen_cpus )
>> + BUG_ON(cpu_notifier_call_chain(cpu, CPU_RESUME_FAILED, NULL));
>> +
>> cpumask_clear(&frozen_cpus);
>> }
>
> Is there a particular reason you add a second loop here?
Yes, I want to know which cpus did come up again.
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
