From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Yang Z Zhang <yang.z.zhang@intel.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Malcolm Crossley <malcolm.crossley@citrix.com>,
Kevin Tian <kevin.tian@intel.com>,
Donald D Dugger <donald.d.dugger@intel.com>
Subject: Re: [PATCH RFC] VT-d: honor firmware-first mode in XSA-59 workaround code
Date: Wed, 21 May 2014 17:33:56 +0100 [thread overview]
Message-ID: <537CD574.3030701@citrix.com> (raw)
In-Reply-To: <537CEBD20200007800014A29@mail.emea.novell.com>
On 21/05/14 17:09, Jan Beulich wrote:
> When firmware-first mode is being indicated by firmware, we shouldn't
> be modifying AER registers - these ar considered to be owned by
"these are"
> firmware in that case. Violating this is being reported to result in
> SMI (or was it SCI?) storms.
SMM livelock.
The exact problem was a 2.6.32 kernel ignoring firmware-first and
disabling reporting on the root ports but not endpoint devices, causing
the SMM handler to fail to find the issue, and fail to clear the SMI.
However, as part of the investigation, we identified that Xen was also
violating firmware-first as part of XSA-59
~Andrew
> While circumventing the workaround means
> re-exposing affected hosts to the XSA-59 issues, this in any event
> seems better than not booting at all. Respective messages are being
> issued to the log, so the situation can be diagnosed.
>
> The basic building blocks were taken from Linux 3.15-rc.
>
> Reported-by: Andrew Cooper <andrew.cooper3@citrix.com>
> Reported-by: Malcolm Crossley <malcolm.crossley@citrix.com>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
next prev parent reply other threads:[~2014-05-21 16:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 16:09 [PATCH RFC] VT-d: honor firmware-first mode in XSA-59 workaround code Jan Beulich
2014-05-21 16:33 ` Andrew Cooper [this message]
2014-05-22 7:13 ` Jan Beulich
2014-05-22 9:34 ` Andrew Cooper
2014-05-22 10:06 ` Jan Beulich
2014-05-22 10:19 ` Andrew Cooper
2014-05-22 10:33 ` Jan Beulich
2014-05-22 14:19 ` Andrew Cooper
2014-05-23 1:03 ` Zhang, Yang Z
2014-05-23 6:13 ` Jan Beulich
2014-05-23 6:40 ` Zhang, Yang Z
2014-05-23 2:32 ` Zhang, Yang Z
2014-05-23 6:22 ` Jan Beulich
2014-05-23 6:46 ` Zhang, Yang Z
2014-05-23 7:15 ` Jan Beulich
2014-05-26 0:39 ` Zhang, Yang Z
2014-05-26 10:19 ` [PATCH v2 " Jan Beulich
2014-06-03 14:38 ` Malcolm Crossley
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=537CD574.3030701@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=donald.d.dugger@intel.com \
--cc=kevin.tian@intel.com \
--cc=malcolm.crossley@citrix.com \
--cc=xen-devel@lists.xenproject.org \
--cc=yang.z.zhang@intel.com \
/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).