From: Jia He <hejianet@gmail.com>
To: Xiongfeng Wang <wangxiongfeng2@huawei.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 13:55:16 +0800 [thread overview]
Message-ID: <adfea83d-fb86-f388-3409-eea9564b938a@gmail.com> (raw)
In-Reply-To: <135ee490-a5a6-46c9-208e-81849b20d6b6@huawei.com>
Hi Xiongfeng
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 for the infor, I guess you used GED device in qemu ;-)?
---
Cheers,
Justin (Jia He)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-07-04 5:55 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 [this message]
2019-07-04 6:04 ` Jia He
2019-07-04 6:17 ` Xiongfeng Wang
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=adfea83d-fb86-f388-3409-eea9564b938a@gmail.com \
--to=hejianet@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=guohanjun@huawei.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=wangxiongfeng2@huawei.com \
--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