From: Ankur Arora <ankur.a.arora@oracle.com>
To: Laszlo Ersek <lersek@redhat.com>, Igor Mammedov <imammedo@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [RFC] ich9:cpuhp: add support for cpu hot-unplug with SMI broadcast enabled
Date: Mon, 30 Nov 2020 11:45:59 -0800 [thread overview]
Message-ID: <930a2917-866c-fb28-5bf6-7b74b6c76869@oracle.com> (raw)
In-Reply-To: <caf7b59e-88e2-4153-1590-7a39e13346f1@redhat.com>
On 2020-11-30 8:58 a.m., Laszlo Ersek wrote:
> On 11/28/20 00:48, Ankur Arora wrote:
>
>> It is possible that there are CPUs with bits for both is_inserting and
>> is_removing. In that case QemuCpuhpCollectApicIds() would put them in the
>> PluggedApicIds array and the unplug eventually happens in the next
>> firmware invocation.
>>
>> If a CPU has both is_inserting and fw_remove set, the firmware processes
>> the
>> hotplug in that invocation and the unplug happens whenever the OSPM
>> triggers
>> the firmware next.
>
> If these corner cases will actually work (I'm somewhat doubtful), that
> will be really great.
Heh, yeah. That's a big if. I'll see if I can hit it in my testing.
Thanks
Ankur
next prev parent reply other threads:[~2020-11-30 19:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 12:25 [RFC] ich9:cpuhp: add support for cpu hot-unplug with SMI broadcast enabled Igor Mammedov
2020-11-24 22:58 ` Laszlo Ersek
2020-11-26 10:24 ` Ankur Arora
2020-11-26 12:46 ` Laszlo Ersek
2020-11-26 19:50 ` Igor Mammedov
2020-11-27 3:39 ` Ankur Arora
2020-11-27 3:35 ` Ankur Arora
2020-11-27 11:33 ` Igor Mammedov
2020-11-27 15:02 ` Laszlo Ersek
2020-11-27 23:48 ` Ankur Arora
2020-11-30 16:58 ` Laszlo Ersek
2020-11-30 19:45 ` Ankur Arora [this message]
2020-11-26 20:45 ` Igor Mammedov
2020-11-26 11:17 ` Laszlo Ersek
2020-11-26 20:38 ` Igor Mammedov
2020-11-27 4:10 ` Ankur Arora
2020-11-27 11:47 ` Igor Mammedov
2020-11-27 23:49 ` Ankur Arora
2020-11-27 15:19 ` Laszlo Ersek
2020-11-28 0:43 ` Ankur Arora
2020-11-30 17:00 ` Laszlo Ersek
2020-11-27 14:48 ` Laszlo Ersek
2020-11-27 15:07 ` Igor Mammedov
2020-11-27 16:52 ` Laszlo Ersek
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=930a2917-866c-fb28-5bf6-7b74b6c76869@oracle.com \
--to=ankur.a.arora@oracle.com \
--cc=imammedo@redhat.com \
--cc=lersek@redhat.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).