From: Paolo Bonzini <pbonzini@redhat.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Jordan Justen <jordan.l.justen@intel.com>,
qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>,
Michael Kinney <michael.d.kinney@intel.com>,
Laszlo Ersek <lersek@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] hw/isa/lpc_ich9: inject the SMI on the VCPU that is writing to APM_CNT
Date: Fri, 23 Oct 2015 19:00:38 +0200 [thread overview]
Message-ID: <562A67B6.1090804@redhat.com> (raw)
In-Reply-To: <20151023165431.GA18431@morn.lan>
On 23/10/2015 18:54, Kevin O'Connor wrote:
>> >
>> > Extra privileges compared to what? Legacy BIOS does not really put
>> > anything privileged in SMRAM, while OVMF does and _hence_ relocates the
>> > SMBASE of the AP. It would have been nice to get it right from the
>> > beginning, but right now it's not worth forcing a lockstep QEMU-SeaBIOS
>> > update.
> We could add code to SeaBIOS now that protects against multiple SMI
> handlers running, and then at some future date QEMU could be updated.
> I'll defer to your judgment if that makes sense.
>
> BTW, how does OVMF handle SMIs on multiple processors? Does it setup
> a unique SMBASE for each cpu, or does it inspect the apic id (or
> something similar) in the smi handler to determine which cpu should
> handle the event?
It does the former.
Paolo
prev parent reply other threads:[~2015-10-23 17:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 18:14 [Qemu-devel] [PATCH] hw/isa/lpc_ich9: inject the SMI on the VCPU that is writing to APM_CNT Laszlo Ersek
2015-10-21 9:49 ` Paolo Bonzini
2015-10-21 10:29 ` Michael S. Tsirkin
2015-10-21 18:36 ` Jordan Justen
2015-10-22 8:40 ` Paolo Bonzini
2015-10-22 9:50 ` Laszlo Ersek
2015-10-22 9:54 ` Paolo Bonzini
2015-10-22 18:04 ` Kevin O'Connor
2015-10-22 19:46 ` Paolo Bonzini
2015-10-23 4:41 ` Jordan Justen
2015-10-23 7:26 ` Paolo Bonzini
2015-10-23 12:53 ` Laszlo Ersek
2015-10-23 18:20 ` Jordan Justen
2015-10-23 18:24 ` Paolo Bonzini
2015-10-23 21:25 ` Laszlo Ersek
2015-10-23 16:54 ` Kevin O'Connor
2015-10-23 17:00 ` Paolo Bonzini [this message]
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=562A67B6.1090804@redhat.com \
--to=pbonzini@redhat.com \
--cc=jordan.l.justen@intel.com \
--cc=kevin@koconnor.net \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=michael.d.kinney@intel.com \
--cc=mst@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).