mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "jroedel@suse.de" <jroedel@suse.de>
To: Felix Kuehling <felix.kuehling@amd.com>
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
	Joerg Roedel <joro@8bytes.org>,
	"iommu@lists.linux-foundation.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" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] iommu/amd: Fix IOMMUv2 devices when SME is active
Date: Fri, 28 Aug 2020 17:27:59 +0200	[thread overview]
Message-ID: <20200828152759.GX3354@suse.de> (raw)
In-Reply-To: <60067932-dbf4-d67b-cf11-4dd2b016ed63@amd.com>

Hi Felix,

On Fri, Aug 28, 2020 at 09:54:59AM -0400, Felix Kuehling wrote:
> Yes, we're working on this. IOMMUv2 is only needed for KFD. It's not
> needed for graphics. And we're making it optional for KFD as well.

Okay, KFD should fail gracefully because it can't initialize the
device's iommuv2 functionality.


Regards,

	Joerg

      parent reply	other threads:[~2020-08-28 15:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-24 10:54 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
     [not found] ` <MN2PR12MB4488D6B7BBF98845DF796E0BF7540@MN2PR12MB4488.namprd12.prod.outlook.com>
2020-08-26 15:22   ` [PATCH 0/2] iommu/amd: Fix IOMMUv2 devices " 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
2020-08-28 15:27           ` jroedel [this message]

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=20200828152759.GX3354@suse.de \
    --to=jroedel@suse.de \
    --cc=Alexander.Deucher@amd.com \
    --cc=Christian.Koenig@amd.com \
    --cc=Ray.Huang@amd.com \
    --cc=Suravee.Suthikulpanit@amd.com \
    --cc=Thomas.Lendacky@amd.com \
    --cc=felix.kuehling@amd.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --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
Powered by JetHome