[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xen-Error: Disabling IOMMU on Stepping C2 5520 Host-Bridge

  • To: Marek Marczykowski-Górecki <marmarek@xxxxxxxxxxxxxxxxxxxxxx>, luja <luja@xxxxxxxxxxxxxxx>
  • From: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  • Date: Tue, 27 Jul 2021 13:21:57 +0100
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=citrix.com; dmarc=pass action=none header.from=citrix.com; dkim=pass header.d=citrix.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=kxwXzCdeGLxyz8buSNUAS85+Iqaxgsc86WelFEVJz4I=; b=a49isahVBflV+qtynM5k2kn7Vg9leyLktgO+Dt2fNmr5XAHUe5RTxCk4buYICz7ia4ZTKdOpiFsBYsDHxZzqcHufCE0a5sTMd4LeEyrb7HqNMuXzXKE7E0iqW4fUdk5R/M+5lheD+w68/NoHGA0x7Bxp7lSx1ol0v+EMcZkDur3CxuGkQf/HnlBTeqyND4BiN8FXAsCso3hWLeW3QMjRkltZJMGHSexTzptJy+M3S42sy+L/ua4kQsuGI0bwpbOs5RAdkv2AK1/xbSi4f04ZWBpF9Ix6kF7Z/QISuLQbapf96ozZRy4txs+bFuoWsqRVPTRVoZyzjOLqn7KfL11xCQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=XOG+6gTlpAM1uPBL/pfDJbWlgNEc7N5n6eE4dDqxu+/jCp4kz7561RBnASkSF6/Y3tuEyomuJwywOq58aKxsWqwySSMwoc2XeUO4hfzqD2HTZnJRm/u2ioupGB+rgI69JRNdqk0xQsGg1BESyXvfPulVt8EeTi72duG+jr9k6u9/uVh/9odx0fV6kJp5u/QKTY0p2+By6Qf3DjIfTmkLU694Ggowmft7Bl2G5THh5sgg6Zd1sQs6SAe2tJWJpEchf42gLLzvCF3acMgfb4k9qlzr58vPHIvunbjIOu/SvJfAQzLlIJG073szY3b7Bc67iGVTRLx8PP8nfCABozOl3g==
  • Authentication-results: esa2.hc3370-68.iphmx.com; dkim=pass (signature verified) header.i=@citrix.onmicrosoft.com
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Tue, 27 Jul 2021 12:22:13 +0000
  • Ironport-hdrordr: A9a23:9Tlx3qDY11LFej/lHegPsceALOsnbusQ8zAXPh9KJCC9I/bzqy nxpp8mPEfP+U0ssHFJo6HiBEDyewKnyXcV2/hfAV7GZmXbUQSTXeZfBOfZogEIXheOjtK1tp 0QPZSWaueAa2SS5PySiGbXLz9j+qj/zEnCv5a9854Zd3APV0gW1XYdNu/0KC1LbTgDIaB8OI uX58JBqTblU28QdN6HCn4MWPWGj8HXlbr9CCR2RyIP2U2rt3eF+bT6Gx+X0lM1SDVU24ov9m DDjkjQ+rijifem0RXRvlWjrKi+2eGRiOerNvb8zvT9GQ+czTpAo74RHYFqiQpF5d1HLmxaye Uk7S1QZ/iboEmhAl1d6SGdpDXI4XIL53j+yVmemxLY0LHErXQBeot8bMtiA2rkA0ZMhqAD7I tbm22erJZZFhXGgWD04MXJTQhjkg6urWMlivN7tQ0UbWIyUs4YkWUkxjIfLH7AJlOP1Kk3VO 11SM3M7vdfdl2XK3jfo2l02dSpGnA+BA2PTEQOstGcl2E+pgE082IIgMgE2nsQ/pM0TJdJo+ zCL6RzjblLCssbd7h0CusNSda+TmbNXRXPOmSPJkmPLtBLB1vd75rspLkl7uCjf5IFiJM0hZ TaSVtd8XU/fkr/YPf+laGjMiq9NllVeA6dv/22y6IJyYEUdYCbRhFrEmpe4/dIi89vcPHmZw ==
  • Ironport-sdr: FuMni91RZuLajulGVyi59JAMd428fUEbhf4cj+ukBdnMIGTT4fwjOrHpkoeR7eiJd8oDK820Bi VyiKztwfDO7jY0oeHeei6OehK5Zv0Q7lye0yU1kqg0/85RRD5yIx+2bjqiMUnc4KFtozbODnoI hNS0VqrO/DShFh849sCc+KzfUcRHB/LOT6o1mYYmcHlGoE0xcUZJgdXoTGdWN9a9g6Q2rl5pON P4SDdKTGUepWR5rc/IxkfgDFwaR7U0A2S06rR00hsHyY2sTJyaDO69hj6womN77l6hV2R8E2Lh 1njsRjTUUPCPuCDmCbS9pfOv
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 25/07/2021 14:55, Marek Marczykowski-Górecki wrote:
> On Sun, Jul 25, 2021 at 02:31:17PM +0200, luja wrote:
>> This Z600 is equipped with 0B54h mainboard as can be seen with dmi-decode.
>> The manual states that 0B54h mainboard has the "newer C2 stepping",
>> so it is *not* affected by Intel "spec update" (nota bene: Intel updates the
>> spec, others report erratas) bugs  
> The code above checks for rev 0x13, and the spec (page 11) clearly says that 
> rev
> 0x13 is stepping B-3. Stepping C-2 is rev 0x22. So, if this check
> triggers for you, I'm afraid you have the affected chipset.

The ID in hardware is the authoritative information.  Sounds like the
Z600 manual is wrong.

>> So the way Xen detects the "bug" (pci rev 13) is not sufficient, as my Z600
>> shows pci rev13 with lspci but 0xB54h (board rev only on Z600) with dmidecode
>> I would suggest first to have an override xen kernel boot option to disable 
>> the disablement in this code section. Or just patch this part out of the Xen 
>> code and rebuild xen. If this stuff really crashes, one will see it.
> Patching it out is out of the question, this check if there for a
> reason.

Using interrupt remapping on these systems does cause it to cease

>> So please build a new xen without this stupid disablement or please add an 
>> override boot command for it.
>> Please see the attached upgrade manual of Z600 and the errata "spec update" 
>> by Intel.
>> You see that the C2 stepping is not affected by the bugs refered to in the 
>> xen code,
>> so removing that section or adding better detection of the mask revision (B3 
>> vs. C2)  of 5520 host bridge would allow  many users to operate Qubes4.
> Maybe someone else has an alternative idea?

The logic in Xen is broken.  I've tried fixing it before for XenServer,
but was objected to, and the patch is still in the patchqueue.

The errata is with the Queued Invalidation, which (in Xen) is tied to
interrupt remapping.  The rest of the IOMMU works fine.

The current status quo is that if Xen boots with an Intel gen1 IOMMU, it
will be happy with DMA remapping but no IRQ remapping.  If Xen boots on
this specific buggy system, it will turn the entire IOMMU off in
protest, which leaves the system less secure than booting on the
previous generation of hardware.

The correct behaviour is to just disable interrupt remapping in this
case, which brings Xen's behaviour in line with adjacent generations of




Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.