From: Felix Kuehling <felix.kuehling@amd.com>
To: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
Joerg Roedel <joro@8bytes.org>
Cc: "Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
"jroedel@suse.de" <jroedel@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"Huang, Ray" <Ray.Huang@amd.com>,
"Koenig, Christian" <Christian.Koenig@amd.com>
Subject: Re: [PATCH 0/2] iommu/amd: Fix IOMMUv2 devices when SME is active
Date: Mon, 7 Sep 2020 23:38:14 -0400 [thread overview]
Message-ID: <61776061-9f26-a3bc-9776-0d1772e2b266@amd.com> (raw)
In-Reply-To: <MN2PR12MB448843EC6D3D5B71613BEAAFF72B0@MN2PR12MB4488.namprd12.prod.outlook.com>
Am 2020-09-06 um 12:08 p.m. schrieb Deucher, Alexander:
> [AMD Official Use Only - Internal Distribution Only]
>
>> -----Original Message-----
>> From: Joerg Roedel <joro@8bytes.org>
>> Sent: Friday, September 4, 2020 6:06 AM
>> To: Deucher, Alexander <Alexander.Deucher@amd.com>
>> Cc: jroedel@suse.de; Kuehling, Felix <Felix.Kuehling@amd.com>;
>> 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:47:07PM +0000, Deucher, Alexander wrote:
>>> Ah, right, So CZ and ST are not an issue. Raven is paired with Zen based
>> CPUs.
>>
>> Okay, so for the Raven case, can you add code to the amdgpu driver which
>> makes it fail to initialize on Raven when SME is active? There is a global
>> checking function for that, so that shouldn't be hard to do.
>>
> Sure. How about the attached patch?
The patch is
Acked-by: Felix Kuehling <Felix.Kuehling@amd.com>
Thanks,
Felix
>
> Alex
>
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-09-08 3:38 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
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 [this message]
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=61776061-9f26-a3bc-9776-0d1772e2b266@amd.com \
--to=felix.kuehling@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=Ray.Huang@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.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).