[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [PATCH v2 04/10] Introduce the CPU address space destruction functio
From: |
Salil Mehta |
Subject: |
RE: [PATCH v2 04/10] Introduce the CPU address space destruction function |
Date: |
Tue, 26 Sep 2023 11:03:53 +0000 |
Hi David,
> From: qemu-devel-bounces+salil.mehta=huawei.com@nongnu.org <qemu-devel-
> bounces+salil.mehta=huawei.com@nongnu.org> On Behalf Of David Hildenbrand
> Sent: Tuesday, September 12, 2023 8:00 AM
> To: xianglai li <lixianglai@loongson.cn>; qemu-devel@nongnu.org
> Cc: Salil Mehta <salil.mehta@opnsrc.net>; Xiaojuan Yang
> <yangxiaojuan@loongson.cn>; Song Gao <gaosong@loongson.cn>; Michael S.
> Tsirkin <mst@redhat.com>; Igor Mammedov <imammedo@redhat.com>; Ani Sinha
> <anisinha@redhat.com>; Paolo Bonzini <pbonzini@redhat.com>; Richard
> Henderson <richard.henderson@linaro.org>; Eduardo Habkost
> <eduardo@habkost.net>; Marcel Apfelbaum <marcel.apfelbaum@gmail.com>;
> Philippe Mathieu-Daudé <philmd@linaro.org>; wangyanan (Y)
> <wangyanan55@huawei.com>; Daniel P. Berrangé <berrange@redhat.com>; Peter
> Xu <peterx@redhat.com>; Bibo Mao <maobibo@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:
20230926100436.28284-1-salil.mehta@huawei.com/T/#m523b37819c4811c7827333982004e07a1ef03879">https://lore.kernel.org/qemu-devel/20230926100436.28284-1-salil.mehta@huawei.com/T/#m523b37819c4811c7827333982004e07a1ef03879
Thanks
Salil.
- Re: [PATCH v2 04/10] Introduce the CPU address space destruction function, (continued)
- Re: [PATCH v2 04/10] Introduce the CPU address space destruction function, lixianglai, 2023/09/14
- Re: [PATCH v2 04/10] Introduce the CPU address space destruction function, David Hildenbrand, 2023/09/14
- Re: [PATCH v2 04/10] Introduce the CPU address space destruction function, lixianglai, 2023/09/14
- Re: [PATCH v2 04/10] Introduce the CPU address space destruction function, lixianglai, 2023/09/14
- Re: [PATCH v2 04/10] Introduce the CPU address space destruction function, David Hildenbrand, 2023/09/15
- Re: [PATCH v2 04/10] Introduce the CPU address space destruction function, lixianglai, 2023/09/15
- Re: [PATCH v2 04/10] Introduce the CPU address space destruction function, Philippe Mathieu-Daudé, 2023/09/15
- Re: [PATCH v2 04/10] Introduce the CPU address space destruction function, David Hildenbrand, 2023/09/15
- RE: [PATCH v2 04/10] Introduce the CPU address space destruction function, Salil Mehta, 2023/09/26
- RE: [PATCH v2 04/10] Introduce the CPU address space destruction function, Salil Mehta, 2023/09/26
- RE: [PATCH v2 04/10] Introduce the CPU address space destruction function,
Salil Mehta <=
[PATCH v2 02/10] Update CPUs AML with cpu-(ctrl)dev change, xianglai li, 2023/09/11
[PATCH v2 01/10] Update ACPI GED framework to support vcpu hot-(un)plug, xianglai li, 2023/09/11
[PATCH v2 06/10] Optimize loongarch_irq_init function implementation, xianglai li, 2023/09/11
[PATCH v2 09/10] Add generic event device for Loongarch, xianglai li, 2023/09/11
[PATCH v2 10/10] Update the ACPI table for the Loongarch CPU, xianglai li, 2023/09/11
RE: [PATCH v2 00/10] Adds CPU hot-plug support to Loongarch, Salil Mehta, 2023/09/12