linux-kernel - RE: [PATCH 0/2] iommu/amd: Fix IOMMUv2 devices when SME is active

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <MN2PR12MB4488BE2F12F85BDBC91E2C0CF7520@MN2PR12MB4488.namprd12.prod.outlook.com>
Date:   Fri, 28 Aug 2020 15:47:07 +0000
From:   "Deucher, Alexander" <Alexander.Deucher@....com>
To:     "jroedel@...e.de" <jroedel@...e.de>
CC:     "Kuehling, Felix" <Felix.Kuehling@....com>,
        Joerg Roedel <joro@...tes.org>,
        "iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>,
        "Huang, Ray" <Ray.Huang@....com>,
        "Koenig, Christian" <Christian.Koenig@....com>,
        "Lendacky, Thomas" <Thomas.Lendacky@....com>,
        "Suthikulpanit, Suravee" <Suravee.Suthikulpanit@....com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 0/2] iommu/amd: Fix IOMMUv2 devices when SME is active

[AMD Public Use]

> -----Original Message-----
> From: jroedel@...e.de <jroedel@...e.de>
> Sent: Friday, August 28, 2020 11:30 AM
> To: Deucher, Alexander <Alexander.Deucher@....com>
> Cc: Kuehling, Felix <Felix.Kuehling@....com>; Joerg Roedel
> <joro@...tes.org>; iommu@...ts.linux-foundation.org; Huang, Ray
> <Ray.Huang@....com>; Koenig, Christian <Christian.Koenig@....com>;
> Lendacky, Thomas <Thomas.Lendacky@....com>; Suthikulpanit, Suravee
> <Suravee.Suthikulpanit@....com>; linux-kernel@...r.kernel.org
> Subject: Re: [PATCH 0/2] iommu/amd: Fix IOMMUv2 devices when SME is
> active
> 
> On Fri, Aug 28, 2020 at 03:11:32PM +0000, Deucher, Alexander wrote:
> > There are hw bugs on Raven and probably Carrizo/Stoney where they need
> > 1:1 mapping to avoid bugs in some corner cases with the displays.
> > Other GPUs should be fine.  The VIDs is 0x1002 and the DIDs are 0x15dd
> > and 0x15d8 for raven variants and 0x9870, 0x9874, 0x9875, 0x9876,
> > 0x9877 and 0x98e4 for carrizo and stoney.  As long as we preserve the
> > 1:1 mapping for those asics, we should be fine.
> 
> Okay, Stoney at least has no Zen-based CPU, so no support for memory
> encryption anyway. How about Raven, is it paired with a Zen CPU?

Ah, right,  So CZ and ST are not an issue.  Raven is paired with Zen based CPUs.

Thanks,

Alex