Hi David, > From: [email protected] <qemu-devel- > [email protected]> On Behalf Of David Hildenbrand > Sent: Tuesday, September 12, 2023 8:00 AM > To: xianglai li <[email protected]>; [email protected] > Cc: Salil Mehta <[email protected]>; Xiaojuan Yang > <[email protected]>; Song Gao <[email protected]>; Michael S. > Tsirkin <[email protected]>; Igor Mammedov <[email protected]>; Ani Sinha > <[email protected]>; Paolo Bonzini <[email protected]>; Richard > Henderson <[email protected]>; Eduardo Habkost > <[email protected]>; Marcel Apfelbaum <[email protected]>; > Philippe Mathieu-Daudé <[email protected]>; wangyanan (Y) > <[email protected]>; Daniel P. Berrangé <[email protected]>; Peter > Xu <[email protected]>; Bibo Mao <[email protected]> > Subject: Re: [PATCH v2 04/10] Introduce the CPU address space destruction > function > > On 12.09.23 04:11, xianglai li wrote: > > Introduce new function to destroy CPU address space resources > > for cpu hot-(un)plug. > > > How do other archs handle that? Or how are they able to get away without > destroying?
This patch-set is based on the ARM RFC. We do destroy AddressSpace there. Is there any reason you are hinting why it should not be done? I have posted the RFC V2 Virtual CPU Hotplug Support on ARM today and You are CC'ed in it. Please have a look at the implementation: https://lore.kernel.org/qemu-devel/[email protected]/T/#m523b37819c4811c7827333982004e07a1ef03879 Thanks Salil.
