On 2015-10-25 19:53:23, Paolo Bonzini wrote:
> On 23/10/2015 17:29, Laszlo Ersek wrote:
> > I plan to drop this patch, dependent on testing, and on how a new QEMU
> > patch I've written will be received on qemu-devel.
>
> I'm not sure why it can't be fixed within the firmware. Your patch
> to
-Original Message-
From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Paolo
Bonzini
Sent: Monday, October 26, 2015 10:53 AM
To: Laszlo Ersek; edk2-de...@ml01.01.org
Cc: Kinney, Michael D; Justen, Jordan L
Subject: Re: [edk2] [PATCH v3 27/52] OvmfPkg: use relaxed AP SMM
o.bonz...@gmail.com] On Behalf Of Paolo
>Bonzini
>Sent: Sunday, October 25, 2015 7:53 PM
>To: Laszlo Ersek; edk2-de...@ml01.01.org
>Cc: Kinney, Michael D; Justen, Jordan L
>Subject: Re: [edk2] [PATCH v3 27/52] OvmfPkg: use relaxed AP SMM
>synchronization mode
>
>On 23/10/2015 1
On 23/10/2015 17:29, Laszlo Ersek wrote:
> I plan to drop this patch, dependent on testing, and on how a new QEMU
> patch I've written will be received on qemu-devel.
I'm not sure why it can't be fixed within the firmware. Your patch
to QEMU to use current_cpu obviously makes sense (that's why
On 10/15/15 00:26, Laszlo Ersek wrote:
> From: Paolo Bonzini
>
> Port 0xb2 on QEMU only sends an SMI to the currently executing processor.
> The SMI handler, however, and in particular SmmWaitForApArrival, currently
> expects that SmmControl2DxeTrigger triggers an SMI IPI on
From: Paolo Bonzini
Port 0xb2 on QEMU only sends an SMI to the currently executing processor.
The SMI handler, however, and in particular SmmWaitForApArrival, currently
expects that SmmControl2DxeTrigger triggers an SMI IPI on all processors
rather than just the BSP. Thus
6 matches
Mail list logo