On Tue, 25 Aug 2020 19:25:48 +0200 Laszlo Ersek <ler...@redhat.com> wrote:
> On 08/18/20 14:22, Igor Mammedov wrote: > > In case firmware has negotiated CPU hotplug SMI feature, generate > > AML to describe SMI IO port region and send SMI to firmware > > on each CPU hotplug SCI in case new CPUs were hotplugged. > > > > Since new CPUs can be hotplugged while CPU_SCAN_METHOD is running > > we can't send SMI before new CPUs are fetched from QEMU as it > > could cause sending Notify to a CPU that firmware hasn't seen yet. > > So fetch new CPUs into local cache first and then send SMI and > > after that sends Notify events to cached CPUs. This should ensure > > that Notify is sent only to CPUs which were processed by firmware > > first. > > Any CPUs that were hotplugged after caching will be processed > > by the next CPU_SCAN_METHOD, when pending SCI is handled. > > > > Signed-off-by: Igor Mammedov <imamm...@redhat.com> > > --- > > v2: > > - clear insert event after firmware has returned > > control from SMI. (Laszlo Ersek <ler...@redhat.com>) Laszlo, Thanks a lot for such detailed review I'll respin series with your feed back incorporated. [...]
