All of lore.kernel.org
 help / color / mirror / Atom feed
From: Malcolm Crossley <malcolm.crossley@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	Joerg Roedel <joro@8bytes.org>,
	Neil Horman <nhorman@tuxdriver.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: VT-d interrup remapping errata workaround
Date: Tue, 9 Jul 2013 10:34:13 +0100	[thread overview]
Message-ID: <51DBD915.6060901@citrix.com> (raw)
In-Reply-To: <51DBCC7E02000078000E3770@nat28.tlf.novell.com>

On 09/07/13 07:40, Jan Beulich wrote:
>>>> On 08.07.13 at 19:11, Neil Horman <nhorman@tuxdriver.com> wrote:
>> Thank you I'll see if I can find an online version to point others to, but
>> regardless, errata 61 seems to be the kicker here.  Looks like we need to add
>> and new pci id to the quirk, and check for some additional revisions if that one
>> is seen.  I'll get to it shortly.  Thanks for sending this out.  Lets hope this
>> problem doesn't exist in even more chipsets.
> Erratum 61? That doesn't require remapping to be disabled as
> workaround. 62 and 69 do.
>
> But you make a very good point regarding revisions: 62 also
> applies to rev 0x12, and 69 applies to both 0x12 and 0x22.
> Xen doesn't check for either of them right now. Malcolm - this
> in turn means that keying off of device ID 0x342e indeed isn't
> correct/complete. Are you going to be able to submit a Xen
> side fix relatively soon, or shall I take care of this?
I didn't notice that errata 69 is not listed as fixed on rev 0x22 for 
the X58
chipset, sorry about that.

Have we had confirmation from Intel about this particular errata affecting
the X58? It seems strange that they both have the same revision ID but
different fixes for errata. If we have got confirmation then I'll create 
a patch
straight away, I'll try our Intel contacts as well, it might speed 
things up a bit.

Malcolm

> Jan
>

  reply	other threads:[~2013-07-09  9:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08 12:29 VT-d interrup remapping errata workaround Jan Beulich
2013-07-08 12:45 ` Malcolm Crossley
2013-07-08 12:56   ` Malcolm Crossley
2013-07-08 13:39   ` Neil Horman
2013-07-08 13:33 ` Neil Horman
2013-07-08 13:42   ` Jan Beulich
2013-07-08 16:22     ` Neil Horman
2013-07-08 17:11     ` Neil Horman
2013-07-09  6:40       ` Jan Beulich
2013-07-09  9:34         ` Malcolm Crossley [this message]
2013-07-09  9:48           ` Jan Beulich
2013-07-08 19:13     ` [RFC PATCH] iommu/vt-d: Expand interrupt remapping quirk to cover x58 chipset Neil Horman
2013-07-09  6:44       ` Jan Beulich

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=51DBD915.6060901@citrix.com \
    --to=malcolm.crossley@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=joro@8bytes.org \
    --cc=nhorman@tuxdriver.com \
    --cc=xen-devel@lists.xen.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 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.