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: Thu, 22 May 2014 15:19:25 +0100 [thread overview]
Message-ID: <537E076D.60700@citrix.com> (raw)
In-Reply-To: <537DEE7D0200007800014E76@mail.emea.novell.com>
On 22/05/14 11:33, Jan Beulich wrote:
>>>> On 22.05.14 at 12:19, <andrew.cooper3@citrix.com> wrote:
>> No. We have not observed an issue from XSA-59.
>>
>> The version of XenServer we had the issue with didn't contain any of the
>> XSA-59 fixes at the point that the problem was observed.
> Then what was yesterday's alert about then? I.e. do we have any
> indication that the workaround as is may cause problems, and that
> hence the (relatively involved) patch here is needed at all? And, how
> are you intending to test this patch if you haven't even seen an
> issue?
>
> Jan
>
As part of finding the root cause of our issue, we identified that just
as Dom0 must not play with AER in firmware first mode, Xen must not play
either.
I believe that we have XSA-59 affected hardware with both firmware-first
and non-firmware-first HEST tables, so we should be able to
behaviourally test the patch.
~Andrew
next prev parent reply other threads:[~2014-05-22 14:19 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 [this message]
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=537E076D.60700@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 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.