AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Alex Deucher <alexander.deucher@amd.com>
Cc: Christian Konig <christian.koenig@amd.com>,
	amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH V2 1/5] drm/amdkfd: ignore crat by default
Date: Fri, 11 Aug 2023 10:41:19 -0300	[thread overview]
Message-ID: <ZNY6f7gUuxw7jXSK@nvidia.com> (raw)
In-Reply-To: <20230807220545.1320198-1-alexander.deucher@amd.com>

On Mon, Aug 07, 2023 at 06:05:41PM -0400, Alex Deucher wrote:
> We are dropping the IOMMUv2 path, so no need to enable this.
> It's often buggy on consumer platforms anyway.
> 
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> ---
>  drivers/gpu/drm/amd/amdkfd/kfd_crat.c | 4 ----
>  1 file changed, 4 deletions(-)

For the series, please can we go ahead with this ASAP?

The iommu side desperately needs the removal of the iommu_v2 private
interface to the GPU.

I'm really glad to see we can just delete the whole thing!

Thanks,
Jason

  parent reply	other threads:[~2023-08-11 13:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07 22:05 [PATCH V2 1/5] drm/amdkfd: ignore crat by default Alex Deucher
2023-08-07 22:05 ` [PATCH V2 2/5] drm/amdkfd: disable IOMMUv2 support for KV/CZ Alex Deucher
2023-08-07 22:05 ` [PATCH V2 3/5] drm/amdkfd: disable IOMMUv2 support for Raven Alex Deucher
2023-08-07 22:05 ` [PATCH V2 4/5] drm/amdkfd: drop IOMMUv2 support Alex Deucher
2023-08-07 22:05 ` [PATCH V2 5/5] drm/amdkfd: rename device_queue_manager_init_v10_navi10() Alex Deucher
2023-08-08 14:59 ` [PATCH V2 1/5] drm/amdkfd: ignore crat by default Christian König
2023-08-08 15:03   ` Mike Lothian
2023-08-08 19:06 ` Felix Kuehling
2023-08-11 13:41 ` Jason Gunthorpe [this message]
2023-08-11 13:46   ` Alex Deucher

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=ZNY6f7gUuxw7jXSK@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    /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