On 01.09.22 14:01, Andrew Cooper wrote:
On 01/09/2022 07:11, Juergen Gross wrote:
On 01.09.22 00:52, Andrew Cooper wrote:
On 16/08/2022 11:13, Juergen Gross wrote:
Cpu cpu unplugging is calling schedule_cpu_rm() via stop_machine_run()
Cpu cpu.
with interrupts disabled, thus any memory allo
On 01/09/2022 07:11, Juergen Gross wrote:
> On 01.09.22 00:52, Andrew Cooper wrote:
>> On 16/08/2022 11:13, Juergen Gross wrote:
>>> Cpu cpu unplugging is calling schedule_cpu_rm() via stop_machine_run()
>>
>> Cpu cpu.
>>
>>> with interrupts disabled, thus any memory allocation or freeing must
>>>
On 01.09.22 00:52, Andrew Cooper wrote:
On 16/08/2022 11:13, Juergen Gross wrote:
Cpu cpu unplugging is calling schedule_cpu_rm() via stop_machine_run()
Cpu cpu.
with interrupts disabled, thus any memory allocation or freeing must
be avoided.
Since commit 5047cd1d5dea ("xen/common: Use enha
On 16/08/2022 11:13, Juergen Gross wrote:
> Cpu cpu unplugging is calling schedule_cpu_rm() via stop_machine_run()
Cpu cpu.
> with interrupts disabled, thus any memory allocation or freeing must
> be avoided.
>
> Since commit 5047cd1d5dea ("xen/common: Use enhanced
> ASSERT_ALLOC_CONTEXT in xmall
Cpu cpu unplugging is calling schedule_cpu_rm() via stop_machine_run()
with interrupts disabled, thus any memory allocation or freeing must
be avoided.
Since commit 5047cd1d5dea ("xen/common: Use enhanced
ASSERT_ALLOC_CONTEXT in xmalloc()") this restriction is being enforced
via an assertion, whic