From: patchwork-bot+linux-riscv@kernel.org
To: Xu Lu <luxu.kernel@bytedance.com>
Cc: linux-riscv@lists.infradead.org, tjeznach@rivosinc.com,
joro@8bytes.org, will@kernel.org, lihangjing@bytedance.com,
xieyongji@bytedance.com, guojinhui.liam@bytedance.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND 0/2] riscv: iommu: Add shutdown callback for kexec
Date: Mon, 03 Feb 2025 19:15:55 +0000 [thread overview]
Message-ID: <173861015549.3409359.6278773851647840223.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250103093220.38106-1-luxu.kernel@bytedance.com>
Hello:
This series was applied to riscv/linux.git (fixes)
by Joerg Roedel <jroedel@suse.de>:
On Fri, 3 Jan 2025 17:32:18 +0800 you wrote:
> After kexec, the newly booted kernel can not initialize iommu driver
> successfully as no one resets iommu state before kexec.
>
> This patch series supplies shutdown callback for iommu driver. The shutdown
> callback resets necessary registers so that newly booted kernel can pass
> riscv_iommu_init_check() after kexec.
>
> [...]
Here is the summary with links:
- [RESEND,1/2] iommu/riscv: Empty iommu queue before enabling it
https://git.kernel.org/riscv/c/8d8d3752c0a4
- [RESEND,2/2] iommu/riscv: Add shutdown function for iommu driver
https://git.kernel.org/riscv/c/77a44196abfb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-02-03 19:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 9:32 [PATCH RESEND 0/2] riscv: iommu: Add shutdown callback for kexec Xu Lu
2025-01-03 9:32 ` [PATCH RESEND 1/2] iommu/riscv: Empty iommu queue before enabling it Xu Lu
2025-01-03 9:32 ` [PATCH RESEND 2/2] iommu/riscv: Add shutdown function for iommu driver Xu Lu
2025-01-06 11:39 ` [PATCH RESEND 0/2] riscv: iommu: Add shutdown callback for kexec Joerg Roedel
2025-02-03 19:15 ` patchwork-bot+linux-riscv [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=173861015549.3409359.6278773851647840223.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=guojinhui.liam@bytedance.com \
--cc=joro@8bytes.org \
--cc=lihangjing@bytedance.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=luxu.kernel@bytedance.com \
--cc=tjeznach@rivosinc.com \
--cc=will@kernel.org \
--cc=xieyongji@bytedance.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