From: Joerg Roedel <joro@8bytes.org>
To: Ashish Kalra <Ashish.Kalra@amd.com>
Cc: suravee.suthikulpanit@amd.com, thomas.lendacky@amd.com,
Sairaj.ArunKodilkar@amd.com, Vasant.Hegde@amd.com,
herbert@gondor.apana.org.au, seanjc@google.com,
pbonzini@redhat.com, will@kernel.org, robin.murphy@arm.com,
john.allen@amd.com, davem@davemloft.net, michael.roth@amd.com,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH v6 0/4] Add host kdump support for SNP
Date: Fri, 5 Sep 2025 14:45:49 +0200 [thread overview]
Message-ID: <aLrbfaoZruWvaAcC@8bytes.org> (raw)
In-Reply-To: <cover.1756157913.git.ashish.kalra@amd.com>
On Mon, Aug 25, 2025 at 09:45:45PM +0000, Ashish Kalra wrote:
> Ashish Kalra (4):
> iommu/amd: Add support to remap/unmap IOMMU buffers for kdump
> iommu/amd: Reuse device table for kdump
> crypto: ccp: Skip SEV and SNP INIT for kdump boot
> iommu/amd: Skip enabling command/event buffers for kdump
>
> drivers/crypto/ccp/sev-dev.c | 10 +
> drivers/iommu/amd/amd_iommu_types.h | 5 +
> drivers/iommu/amd/init.c | 284 +++++++++++++++++++---------
> drivers/iommu/amd/iommu.c | 2 +-
> 4 files changed, 209 insertions(+), 92 deletions(-)
Applied, thanks.
prev parent reply other threads:[~2025-09-05 12:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 21:45 [PATCH v6 0/4] Add host kdump support for SNP Ashish Kalra
2025-08-25 21:46 ` [PATCH v6 1/4] iommu/amd: Add support to remap/unmap IOMMU buffers for kdump Ashish Kalra
2025-08-25 21:46 ` [PATCH v6 2/4] iommu/amd: Reuse device table " Ashish Kalra
2025-08-25 21:46 ` [PATCH v6 3/4] crypto: ccp: Skip SEV and SNP INIT for kdump boot Ashish Kalra
2025-08-25 21:46 ` [PATCH v6 4/4] iommu/amd: Skip enabling command/event buffers for kdump Ashish Kalra
2025-09-05 12:45 ` Joerg Roedel [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=aLrbfaoZruWvaAcC@8bytes.org \
--to=joro@8bytes.org \
--cc=Ashish.Kalra@amd.com \
--cc=Sairaj.ArunKodilkar@amd.com \
--cc=Vasant.Hegde@amd.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=iommu@lists.linux.dev \
--cc=john.allen@amd.com \
--cc=kvm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.roth@amd.com \
--cc=pbonzini@redhat.com \
--cc=robin.murphy@arm.com \
--cc=seanjc@google.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=thomas.lendacky@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;
as well as URLs for NNTP newsgroup(s).