All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
	Anshul Makkar <anshul.makkar@citrix.com>,
	Malcolm Crossley <malcolm.crossley@citrix.com>
Cc: yang.z.zhang@intel.com, kevin.tian@intel.com, xen-devel@lists.xen.org
Subject: Re: [PATCH] iommu/quirk: disable shared EPT for Sandybridge and earlier processors.
Date: Thu, 26 Nov 2015 10:27:13 +0000	[thread overview]
Message-ID: <5656DE81.1010509@citrix.com> (raw)
In-Reply-To: <5656D4C802000078000B9427@prv-mh.provo.novell.com>

On 26/11/15 08:45, Jan Beulich wrote:
>>>> On 25.11.15 at 16:58, <malcolm.crossley@citrix.com> wrote:
>> On 25/11/15 15:38, Jan Beulich wrote:
>>>>>> On 25.11.15 at 16:13, <andrew.cooper3@citrix.com> wrote:
>>>> On 25/11/15 10:49, Jan Beulich wrote:
>>>>> And finally I'm not fully convinced using CPU model info to deduce
>>>>> chipset behavior is entirely correct (albeit perhaps in practice it'll
>>>>> be fine except maybe when running Xen itself virtualized).
>>>> What else would you suggest? I can't think of any better identifying
>>>> information.
>>> Chipset IDs / revisions?
>> In this case the IOMMU is integrated into the Sandybridge-EP processor 
>> itself.
> Which doesn't preclude it to be identified via PCI device ID - after all
> there are dozens of processor integrated PCI devices. Looking at
> one of my systems,
>
> 00:05.0 System peripheral [0880]: Intel Corporation Sandy Bridge Address Map, VTd_Misc, System Management [8086:3c28] (rev 07)
> 80:05.0 System peripheral [0880]: Intel Corporation Sandy Bridge Address Map, VTd_Misc, System Management [8086:3c28] (rev 07)
>
> could be a candidate (we already key a quirk on this device in
> pci_vtd_quirk()).

These are fine for server variants, but not for desktop variants, both
of which we have seen in use.

~Andrew

  reply	other threads:[~2015-11-26 10:27 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-24 17:17 [PATCH] iommu/quirk: disable shared EPT for Sandybridge and earlier processors Anshul
2015-11-24 17:41 ` Jan Beulich
2015-11-25 10:28   ` Andrew Cooper
2015-11-25 10:49     ` Jan Beulich
2015-11-25 15:13       ` Andrew Cooper
2015-11-25 15:38         ` Jan Beulich
2015-11-25 15:58           ` Malcolm Crossley
2015-11-26  7:17             ` Tian, Kevin
2015-12-01 16:45               ` Anshul Makkar
2015-12-01 17:20                 ` Jan Beulich
2015-11-26  8:45             ` Jan Beulich
2015-11-26 10:27               ` Andrew Cooper [this message]
2015-11-26 10:39                 ` Jan Beulich
2015-11-26 11:42                   ` Andrew Cooper
2015-11-26 11:53                     ` Jan Beulich
2015-11-26 13:46     ` Jan Beulich
2015-11-26 13:48       ` Malcolm Crossley
2015-11-26 13:55         ` Andrew Cooper
2015-11-30 21:22           ` Konrad Rzeszutek Wilk
2015-12-01 10:34             ` Andrew Cooper
2015-12-01 10:44               ` Anshul Makkar
2015-12-01 15:24               ` Konrad Rzeszutek Wilk
2015-12-01 16:19                 ` Andrew Cooper
2015-12-03  1:19           ` Tian, Kevin
2015-12-03 11:24             ` Andrew Cooper
2015-12-04  1:55               ` Tian, Kevin
2015-12-03  2:40           ` Tian, Kevin
2015-12-03  8:18             ` Jan Beulich
2015-12-03  8:50               ` Tian, Kevin
2015-12-03 11:19                 ` Andrew Cooper
2015-12-04  2:35                   ` Tian, Kevin
     [not found] <1440776507-30218-1-git-send-email-anshul.makkar@citrix.com>
2015-08-28 16:24 ` Andrew Cooper
2015-08-31  8:09 ` Jan Beulich
2015-09-01 14:18   ` Andrew Cooper
2015-09-01 14:55     ` 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=5656DE81.1010509@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=anshul.makkar@citrix.com \
    --cc=kevin.tian@intel.com \
    --cc=malcolm.crossley@citrix.com \
    --cc=xen-devel@lists.xen.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.