public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Vasant Hegde <vasant.hegde@amd.com>
Cc: Sairaj Kodilkar <sarunkod@amd.com>,
	iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
	joro@8bytes.org, suravee.suthikulpanit@amd.com,
	robin.murphy@arm.com, ashish.kalra@amd.com, will@kernel.org
Subject: Re: [PATCH v2 1/2] amd/iommu: Preserve domain ids inside the kdump kernel
Date: Wed, 26 Nov 2025 11:20:40 -0400	[thread overview]
Message-ID: <20251126152040.GH520526@nvidia.com> (raw)
In-Reply-To: <b15c4495-3765-4af4-8cf1-38c64e8fa69e@amd.com>

On Wed, Nov 26, 2025 at 01:51:27PM +0530, Vasant Hegde wrote:
> It looks like on non-SNP system in kdump path, if it fails to reserve old DTE
> table, it tries to allocate new one! Looking into code again, it may be OK to
> fail in that path as well.. so that we will have common flow.

If it allocates a new (empty) one and does a full flush of the iommu
that would be OK?

Jason

  reply	other threads:[~2025-11-26 15:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-21  9:11 [PATCH v2 0/2] amd/iommu: Preserve domain ids inside the kdump kernel Sairaj Kodilkar
2025-11-21  9:11 ` [PATCH v2 1/2] " Sairaj Kodilkar
2025-11-24 14:44   ` Jason Gunthorpe
2025-11-25  6:32     ` Sairaj Kodilkar
2025-11-26  8:21     ` Vasant Hegde
2025-11-26 15:20       ` Jason Gunthorpe [this message]
2025-12-02  5:21         ` Vasant Hegde
2025-11-21  9:11 ` [PATCH v2 2/2] amd/iommu: Make protection domain ID functions non-static Sairaj Kodilkar
2025-12-02  5:23 ` [PATCH v2 0/2] amd/iommu: Preserve domain ids inside the kdump kernel Vasant Hegde
2025-12-19 10:29   ` Joerg Roedel

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=20251126152040.GH520526@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=ashish.kalra@amd.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=sarunkod@amd.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=vasant.hegde@amd.com \
    --cc=will@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