From: "Deucher, Alexander" <Alexander.Deucher@amd.com>
To: "jroedel@suse.de" <jroedel@suse.de>
Cc: "Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
"Kuehling, Felix" <Felix.Kuehling@amd.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Koenig, Christian" <Christian.Koenig@amd.com>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"Huang, Ray" <Ray.Huang@amd.com>
Subject: RE: [PATCH 0/2] iommu/amd: Fix IOMMUv2 devices when SME is active
Date: Fri, 28 Aug 2020 15:47:07 +0000 [thread overview]
Message-ID: <MN2PR12MB4488BE2F12F85BDBC91E2C0CF7520@MN2PR12MB4488.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20200828152943.GY3354@suse.de>
[AMD Public Use]
> -----Original Message-----
> From: jroedel@suse.de <jroedel@suse.de>
> Sent: Friday, August 28, 2020 11:30 AM
> To: Deucher, Alexander <Alexander.Deucher@amd.com>
> Cc: Kuehling, Felix <Felix.Kuehling@amd.com>; Joerg Roedel
> <joro@8bytes.org>; iommu@lists.linux-foundation.org; Huang, Ray
> <Ray.Huang@amd.com>; Koenig, Christian <Christian.Koenig@amd.com>;
> Lendacky, Thomas <Thomas.Lendacky@amd.com>; Suthikulpanit, Suravee
> <Suravee.Suthikulpanit@amd.com>; linux-kernel@vger.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
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-08-28 15:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 10:54 [PATCH 0/2] iommu/amd: Fix IOMMUv2 devices when SME is active Joerg Roedel
2020-08-24 10:54 ` [PATCH 1/2] iommu/amd: Do not force direct mapping " Joerg Roedel
2020-08-26 14:23 ` Deucher, Alexander
2020-08-24 10:54 ` [PATCH 2/2] iommu/amd: Do not use IOMMUv2 functionality " Joerg Roedel
2020-08-26 14:20 ` Deucher, Alexander
2020-08-26 14:14 ` [PATCH 0/2] iommu/amd: Fix IOMMUv2 devices " Deucher, Alexander
2020-08-26 15:22 ` Felix Kuehling
2020-08-26 15:25 ` Deucher, Alexander
2020-08-28 13:46 ` jroedel
2020-08-28 13:54 ` Felix Kuehling
2020-08-28 15:11 ` Deucher, Alexander
2020-08-28 15:29 ` jroedel
2020-08-28 15:47 ` Deucher, Alexander [this message]
2020-09-04 10:05 ` Joerg Roedel
2020-09-06 16:08 ` Deucher, Alexander
2020-09-07 10:44 ` Joerg Roedel
2020-09-07 11:10 ` Christian König
2020-09-08 3:38 ` Felix Kuehling
2020-08-28 15:27 ` jroedel
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=MN2PR12MB4488BE2F12F85BDBC91E2C0CF7520@MN2PR12MB4488.namprd12.prod.outlook.com \
--to=alexander.deucher@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=Felix.Kuehling@amd.com \
--cc=Ray.Huang@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).