qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	qemu devel list <qemu-devel@nongnu.org>,
	Michael Roth <mdroth@linux.vnet.ibm.com>,
	qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] hw/isa/lpc_ich9: inject SMI on all VCPUs if APM_STS == 'Q'
Date: Wed, 16 Nov 2016 07:47:42 -0500 (EST)	[thread overview]
Message-ID: <1055353985.13082457.1479300462972.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <5a5fce10-9513-c349-a7b0-0931de271322@redhat.com>


> If the consensus is that the patch is a QEMU bugfix (as opposed to a
> feature) and that it is eligible for the currently supported upstream
> stable branches, that's the best, no doubt.

The currently supported upstream stable branches is just 2.7. :)

I'm okay with bending the rules and including it in 2.8, but it's
worrisome that you also needed to go back from relaxed to traditional
delivery, meaning that old QEMU + new OVMF will take ages to boot.

If this is the case, I still think this needs some kind of discovery
mechanism, unless OVMF can just say "things were too broken, stop
supporting SMM on QEMUs older than 2.8".

For example:

- OVMF should keep on using 0x00 (no broadcast) if the relaxed AP
setting is used for the PCD; this would be backwards compatibility mode.

- we could have another magic 0xB2 value, which is implemented directly
in QEMU and sets 0xB3 to a magic value.  Then OVMF can invoke it
after SMBASE relocation and SMM IPL (so as not to crash on old QEMUs)
to detect the new feature.  It can fail to start if using traditional
AP and the new feature is not there.

By the way, in case OVMF needs to use SmmSwDispatch in the future, I
would make QEMU use broadcast behavior for all values in the 0x10-0xff
range, or something like that.

Paolo

> For reference, the OVMF documentation recommends QEMU 2.5+ for SMM. The
> SMM enablement in libvirt enforces QEMU 2.4+. (Libvirt is actually
> correct; when I was writing the OVMF docs, I must have misunderstood the
> requirements and needlessly required 2.5+; 2.4+ should have been fine.)
> 
> Which means the fix should be backported as far as stable-2.4.
> 
> Should we proceed with that? CC'ing Mike Roth and the stable list.
> 
> Thanks!
> Laszlo
> 
> > 
> > 
> >>>
> >>> Paolo
> >>>
> >>>> ---
> >>>>  hw/isa/lpc_ich9.c | 12 +++++++++++-
> >>>>  1 file changed, 11 insertions(+), 1 deletion(-)
> >>>>
> >>>> diff --git a/hw/isa/lpc_ich9.c b/hw/isa/lpc_ich9.c
> >>>> index 10d1ee8b9310..f2fe644fdaa4 100644
> >>>> --- a/hw/isa/lpc_ich9.c
> >>>> +++ b/hw/isa/lpc_ich9.c
> >>>> @@ -372,6 +372,8 @@ void ich9_lpc_pm_init(PCIDevice *lpc_pci, bool
> >>>> smm_enabled)
> >>>>  
> >>>>  /* APM */
> >>>>  
> >>>> +#define QEMU_ICH9_APM_STS_BROADCAST_SMI 'Q'
> >>>> +
> >>>>  static void ich9_apm_ctrl_changed(uint32_t val, void *arg)
> >>>>  {
> >>>>      ICH9LPCState *lpc = arg;
> >>>> @@ -386,7 +388,15 @@ static void ich9_apm_ctrl_changed(uint32_t val,
> >>>> void *arg)
> >>>>  
> >>>>      /* SMI_EN = PMBASE + 30. SMI control and enable register */
> >>>>      if (lpc->pm.smi_en & ICH9_PMIO_SMI_EN_APMC_EN) {
> >>>> -        cpu_interrupt(current_cpu, CPU_INTERRUPT_SMI);
> >>>> +        if (lpc->apm.apms == QEMU_ICH9_APM_STS_BROADCAST_SMI) {
> >>>> +            CPUState *cs;
> >>>> +
> >>>> +            CPU_FOREACH(cs) {
> >>>> +                cpu_interrupt(cs, CPU_INTERRUPT_SMI);
> >>>> +            }
> >>>> +        } else {
> >>>> +            cpu_interrupt(current_cpu, CPU_INTERRUPT_SMI);
> >>>> +        }
> >>>>      }
> >>>>  }
> >>>>  
> >>>>
> 
> 

  reply	other threads:[~2016-11-16 12:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-15  1:50 [Qemu-devel] [PATCH v2] hw/isa/lpc_ich9: inject SMI on all VCPUs if APM_STS == 'Q' Laszlo Ersek
2016-11-15 13:59 ` Paolo Bonzini
2016-11-15 15:39   ` Laszlo Ersek
2016-11-15 15:45     ` Michael S. Tsirkin
2016-11-15 16:40       ` Laszlo Ersek
2016-11-16 12:47         ` Paolo Bonzini [this message]
2016-11-16 13:18           ` Michael S. Tsirkin
2016-11-16 14:05             ` Paolo Bonzini
2016-11-16 18:03               ` Laszlo Ersek
2016-11-16 20:27                 ` Michael S. Tsirkin
2016-11-17 13:16                   ` Laszlo Ersek
2016-11-17 17:46                     ` Michael S. Tsirkin
2016-11-17 18:45                       ` Laszlo Ersek
2016-11-16 17:56             ` Laszlo Ersek
2016-11-16 17:37           ` Laszlo Ersek
2016-11-16 18:04             ` Paolo Bonzini
2016-11-16 18:50               ` Laszlo Ersek
2016-11-16 20:38               ` Michael S. Tsirkin
2016-11-17  9:26                 ` Laszlo Ersek
2016-11-16 20:32             ` Michael S. Tsirkin

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=1055353985.13082457.1479300462972.JavaMail.zimbra@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=lersek@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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).