All of lore.kernel.org
 help / color / mirror / Atom feed
From: Malcolm Crossley <malcolm.crossley@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Yang Z Zhang <yang.z.zhang@intel.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	Kevin Tian <kevin.tian@intel.com>,
	Donald D Dugger <donald.d.dugger@intel.com>
Subject: Re: [PATCH v2 RFC] VT-d: honor firmware-first mode in XSA-59 workaround code
Date: Tue, 3 Jun 2014 15:38:56 +0100	[thread overview]
Message-ID: <538DDE00.8030500@citrix.com> (raw)
In-Reply-To: <538331390200007800015B4F@mail.emea.novell.com>

On 26/05/14 11:19, Jan Beulich wrote:
> When firmware-first mode is being indicated by firmware, we shouldn't
> be modifying AER registers - these are considered to be owned by
> firmware in that case. Violating this is being reported to result in
> SMI storms. 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. Note that
> this includes a block of code enclosed in #ifdef CONFIG_X86_MCE - we
> don't define that symbol, and that code also wouldn't build without
> suitable machine check side code added; that should happen eventually,
> but isn't subject of this change.
> 
> Reported-by: Andrew Cooper <andrew.cooper3@citrix.com>
> Reported-by: Malcolm Crossley <malcolm.crossley@citrix.com>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>

Tested-by: Malcolm Crossley <malcolm.crossley@citrix.com>

> ---
> v2: Only check firmware-first for actual AER (i.e. ignore it for host
>     bridges in DMI mode). Use MASK_EXTR() instead of open coding it.
>     Re-word message from "cannot" to "must not".

I tested this patch on an Dell R810 BIOS version 2.7.4, it successfully
detected the firmware first mode and did not mask device 0000:00:00.0.

The other root ports already had the relevant AER errors masked.

(XEN) Must not mask UR signaling on 0000:00:00.0
(XEN) PCI add device 0000:00:00.0
(XEN) Found masked UR signaling on 0000:00:01.0
(XEN) PCI add device 0000:00:01.0
(XEN) Found masked UR signaling on 0000:00:02.0
(XEN) PCI add device 0000:00:02.0
(XEN) Found masked UR signaling on 0000:00:03.0
(XEN) PCI add device 0000:00:03.0
(XEN) Found masked UR signaling on 0000:00:05.0
(XEN) PCI add device 0000:00:05.0
(XEN) Found masked UR signaling on 0000:00:07.0
(XEN) PCI add device 0000:00:07.0
(XEN) Found masked UR signaling on 0000:00:09.0
(XEN) PCI add device 0000:00:09.0
(XEN) Masked VT-d error signaling on 0000:00:14.0

lspci -n output for Dell R810:

00:00.0 0600: 8086:3407 (rev 22)
00:01.0 0604: 8086:3408 (rev 22)
00:02.0 0604: 8086:3409 (rev 22)
00:03.0 0604: 8086:340a (rev 22)
00:05.0 0604: 8086:340c (rev 22)
00:07.0 0604: 8086:340e (rev 22)
00:09.0 0604: 8086:3410 (rev 22)
00:14.0 0800: 8086:342e (rev 22)
00:14.1 0800: 8086:3422 (rev 22)
00:14.2 0800: 8086:3423 (rev 22)

      reply	other threads:[~2014-06-03 14:39 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
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 [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=538DDE00.8030500@citrix.com \
    --to=malcolm.crossley@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=donald.d.dugger@intel.com \
    --cc=kevin.tian@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.