From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "Keir (Xen.org)" <keir@xen.org>,
Xiantao Zhang <xiantao.zhang@intel.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH 2 of 2] x86/VT-d: Sandy-Bridge BT98 Erratum
Date: Mon, 29 Apr 2013 16:23:36 +0100 [thread overview]
Message-ID: <517E9078.2000805@citrix.com> (raw)
In-Reply-To: <517EAA2C02000078000D1BF7@nat28.tlf.novell.com>
On 29/04/13 16:13, Jan Beulich wrote:
>>>> On 26.04.13 at 20:11, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
>> @@ -288,9 +309,12 @@ void __init platform_quirks_init(void)
>> /* ioremap IGD MMIO+0x2000 page */
>> map_igd_reg();
>>
>> - /* Tylersburg interrupt remap quirk */
>> + /* Interrupt remapping quirks */
>> if ( iommu_intremap )
>> + {
>> tylersburg_intremap_quirk();
>> + snb_bt98_erratum();
>> + }
> Considering the nature of the erratum, keying this off
> iommu_intremap seems wrong - iommu_qinval ought to be used
> instead - intel_vtd_setup() takes care to disable interrupt
> remapping when queued invalidation is not available, yet when
> you make the above conditional upon iommu_intremap, queued
> invalidation could still get enabled (and used for whatever else
> purposes, now or in the future).
>
> Jan
>
Yes - I mentally had the erratum the wrong way around, as intremap is
the visible impact of it.
I shall respin once hearing back from Xiantao, especially regarding the
first patch.
~Andrew
next prev parent reply other threads:[~2013-04-29 15:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 18:11 [PATCH 1 of 2] x86/x2apic: Sandy-Bridge BT98 Erratum Andrew Cooper
2013-04-26 18:11 ` [PATCH 2 of 2] x86/VT-d: " Andrew Cooper
2013-04-29 15:13 ` Jan Beulich
2013-04-29 15:23 ` Andrew Cooper [this message]
2013-04-29 9:04 ` [PATCH 1 of 2] x86/x2apic: " Jan Beulich
2013-04-29 10:25 ` Andrew Cooper
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=517E9078.2000805@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xen.org \
--cc=xiantao.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.