Hi David, > From: qemu-devel-bounces+salil.mehta=huawei....@nongnu.org <qemu-devel- > bounces+salil.mehta=huawei....@nongnu.org> On Behalf Of David Hildenbrand > Sent: Tuesday, September 12, 2023 8:00 AM > To: xianglai li <lixiang...@loongson.cn>; qemu-devel@nongnu.org > Cc: Salil Mehta <salil.me...@opnsrc.net>; Xiaojuan Yang > <yangxiaoj...@loongson.cn>; Song Gao <gaos...@loongson.cn>; Michael S. > Tsirkin <m...@redhat.com>; Igor Mammedov <imamm...@redhat.com>; Ani Sinha > <anisi...@redhat.com>; Paolo Bonzini <pbonz...@redhat.com>; Richard > Henderson <richard.hender...@linaro.org>; Eduardo Habkost > <edua...@habkost.net>; Marcel Apfelbaum <marcel.apfelb...@gmail.com>; > Philippe Mathieu-Daudé <phi...@linaro.org>; wangyanan (Y) > <wangyana...@huawei.com>; Daniel P. Berrangé <berra...@redhat.com>; Peter > Xu <pet...@redhat.com>; Bibo Mao <maob...@loongson.cn> > 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/20230926100436.28284-1-salil.me...@huawei.com/T/#m523b37819c4811c7827333982004e07a1ef03879 Thanks Salil.
