From: Xiongfeng Wang <wangxiongfeng2@huawei.com>
To: Jia He <hejianet@gmail.com>, <rjw@rjwysocki.net>,
<catalin.marinas@arm.com>, <james.morse@arm.com>
Cc: xiexiuqi@huawei.com, jonathan.cameron@huawei.com,
john.garry@huawei.com, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, huawei.libin@huawei.com,
guohanjun@huawei.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RFC 0/3] Support CPU hotplug for ARM64
Date: Thu, 4 Jul 2019 14:17:46 +0800 [thread overview]
Message-ID: <e9acd13e-2501-4b62-496d-e8a5cb872191@huawei.com> (raw)
In-Reply-To: <7898e483-a8e4-39a2-358f-8fcf838c242f@gmail.com>
On 2019/7/4 14:04, Jia He wrote:
> Hi Xiongfeng
>
> Sorry, I missed your latter mail, you used a emulated SCI interrupt
Yes, I only used a emulated SCI interrupt. My colleague is working on the qemu part.
He used the GED device in qemu. But there is still some other issues with the qemu
and he is working on it.
>
> ---
> Cheers,
> Justin (Jia He)
>
> On 2019/7/4 11:26, Xiongfeng Wang wrote:
>> Hi Justin,
>>
>> On 2019/7/4 11:00, Jia He wrote:
>>> Hi Xiongfeng
>>>
>>> It is a little bit awkful that I am also investigating acpi based cpu hotplug issue silimar with
>>>
>>> your idea. My question is your purpose to implement the vcpu hotplug in arm64 qemu?
>> Yes, my purpose is to implement the vcpu hotplug in arm64 qemu. So that I can add or remove vcpu
>> without shutting down the Guest OS.
>>
>> Thanks,
>> Xiongfeng
>>
>>> Thanks for the ellaboration
>>>
>>> ---
>>> Cheers,
>>> Justin (Jia He)
>>>
>>> On 2019/6/28 19:13, Xiongfeng Wang wrote:
>>>> This patchset mark all the GICC node in MADT as possible CPUs even though it
>>>> is disabled. But only those enabled GICC node are marked as present CPUs.
>>>> So that kernel will initialize some CPU related data structure in advance before
>>>> the CPU is actually hot added into the system. This patchset also implement
>>>> 'acpi_(un)map_cpu()' and 'arch_(un)register_cpu()' for ARM64. These functions are
>>>> needed to enable CPU hotplug.
>>>>
>>>> To support CPU hotplug, we need to add all the possible GICC node in MADT
>>>> including those CPUs that are not present but may be hot added later. Those
>>>> CPUs are marked as disabled in GICC nodes.
>>>>
>>>> Xiongfeng Wang (3):
>>>> ACPI / scan: evaluate _STA for processors declared via ASL Device
>>>> statement
>>>> arm64: mark all the GICC nodes in MADT as possible cpu
>>>> arm64: Add CPU hotplug support
>>>>
>>>> arch/arm64/kernel/acpi.c | 22 ++++++++++++++++++++++
>>>> arch/arm64/kernel/setup.c | 19 ++++++++++++++++++-
>>>> arch/arm64/kernel/smp.c | 11 +++++------
>>>> drivers/acpi/scan.c | 12 ++++++++++++
>>>> 4 files changed, 57 insertions(+), 7 deletions(-)
>>>>
>>> .
>>>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-07-04 6:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 11:13 [PATCH RFC 0/3] Support CPU hotplug for ARM64 Xiongfeng Wang
2019-06-28 11:13 ` [PATCH RFC 1/3] ACPI / scan: evaluate _STA for processors declared via ASL Device statement Xiongfeng Wang
2019-06-28 11:13 ` [PATCH RFC 2/3] arm64: mark all the GICC nodes in MADT as possible cpu Xiongfeng Wang
2019-06-28 11:13 ` [PATCH RFC 3/3] arm64: Add CPU hotplug support Xiongfeng Wang
2019-06-29 2:07 ` [PATCH RFC 0/3] Support CPU hotplug for ARM64 Xiongfeng Wang
2019-07-04 3:00 ` Jia He
2019-07-04 3:26 ` Xiongfeng Wang
2019-07-04 5:55 ` Jia He
2019-07-04 6:04 ` Jia He
2019-07-04 6:17 ` Xiongfeng Wang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e9acd13e-2501-4b62-496d-e8a5cb872191@huawei.com \
--to=wangxiongfeng2@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=guohanjun@huawei.com \
--cc=hejianet@gmail.com \
--cc=huawei.libin@huawei.com \
--cc=james.morse@arm.com \
--cc=john.garry@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=xiexiuqi@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox