iommu/arm-smmu-v3: Adopt the crashed kernel's stream table for kdump
Subsystems (2)
v8 cover iommu/arm-smmu-v3: Adopt the crashed kernel's stream table for kdump
When transitioning to a kdump kernel, the primary kernel might have crashed while endpoint devices were actively bus-mastering DMA. Currently, the SMMU driver aggressively resets the hardware during probe by clearing CR0_SMMUEN and setting the Global Bypass Attribute (GBPA) to ABORT.
In a kdump scenario, this aggressive reset is highly destructive:
a) If GBPA is set to ABORT, in-flight DMA will be aborted, generating fatal PCIe AER or SErrors that may panic the kdump kernel
b) If GBPA is set to BYPASS, in-flight DMA targeting some IOVAs will bypass the SMMU and corrupt the physical memory at those 1:1 mapped IOVAs.
To safely absorb in-flight DMA, the kdump kernel must leave SMMUEN=1 intact and avoid modifying STRTAB_BASE. This allows HW to continue translating in- flight DMA using the crashed kernel's page tables until the endpoint device drivers probe and quiesce their respective hardware.
However, the ARM SMMUv3 architecture specification states that updating the SMMU_STRTAB_BASE register while SMMUEN == 1 is UNPREDICTABLE or ignored.
This leaves a kdump kernel no choice but to adopt the stream table from the crashed kernel.
In this series:
- Introduce an ARM_SMMU_OPT_KDUMP_ADOPT
- Skip SMMUEN and STRTAB_BASE resets in arm_smmu_device_reset()
- Skip EVENTQ/PRIQ setup including interrupts and their handlers
- Memremap the crashed kernel's stream tables into the kdump kernel [*]
- Reserve the crashed kernel's in-use ASIDs and VMIDs, preventing any TLB aliasing with the kdump kernel's own domains
- Defer any default domain attachment to retain STEs until device drivers explicitly request it.
Most of the kdump code is added to a new arm-smmu-v3-kdump.c that is only built when CONFIG_CRASH_DUMP is enabled.
[*] For verification reasons, this series only fixes coherent SMMUs.
For non-ARM_SMMU_OPT_KDUMP_ADOPT cases, keep a status quo since the commit 3f54c447df34f ("iommu/arm-smmu-v3: Don't disable SMMU in kdump kernel"):
full reset followed by driver-initiated reattach, potentially rejecting any in-flight DMA.
Note that this series is no longer treated as a bug fix, since it has grown fairly big and most of the kdump code now resides in a separate file. For folks interested in back-porting the change: a v6.12+ kernel (since commit 85196f54743d ("iommu/arm-smmu-v3: Reorganize struct arm_smmu_strtab_cfg")) would be still compatible with this series.
This is on Github:
https://github.com/nicolinc/iommufd/commits/smmuv3_kdump-v8
Changelog
v8
* Move the kdump code into a new arm-smmu-v3-kdump.c
* Move the EVTQ/PRIQ patches to the front of the series
* Prefix "kdump: " to prints via dev_fmt in the new file
* Add a prep patch destroying the vmid_map ida via devres
* Reject valid-span L1 descriptors with a null L2 pointer
* Document notes/limitations at the top of arm-smmu-v3-kdump.c
* Rename arm_smmu_kdump_adopt_l2_strtab() to a deferred variant
* Add a new patch reserving the crashed kernel's ASIDs and VMIDs
* Make arm_smmu_get_step_for_sid() a static inline in the header
* Validate alignments of the adopted stream table base addresses
* Retarget to the merge window; drop the Fixes and Cc-stable tags
* Rename the kdump probe function to arm_smmu_device_kdump_probe()
* Document that a disabled event queue discards new events silently
* Add a common arm_smmu_is_attach_deferred() calling a kdump helper
* Document that acking SFM_ERR is defined but does not exit the SFM
* Document that CR0 queue enables can be cleared while SMMUEN is set
* Clear only the CR0 queue enables in kdump reset, keeping other fields
v7
https://lore.kernel.org/all/[email protected]/
* Rebase v7.2-rc1
* Add Reviewed-by from Pranjal
* Reword the linear stream table adoption comment
* Use dev_dbg for the stream table adoption message
* Document why the lazy L2 adoption uses devm_memremap()
* Drop redundant FEAT_COHERENCY checks in the adopt functions
* Use feature bit instead of STRTAB_BASE_CFG in adopt cleanup
* Skip CR0_ATSCHK update in adopt mode to retain the crashed policy
* Restore FEAT_2_LVL_STRTAB if the cleanup action fails to register
v6
https://lore.kernel.org/all/[email protected]/
* Rebase v7.1-rc3
* Add Reviewed-by from Jason
* Replace dma_addr_t with phys_addr_t
* Drop arm_smmu_kdump_phys_is_corrupted()
* Skip threaded IRQ handlers for EVTQ and PRIQ
* Bypass arm_smmu_rmr_install_bypass_ste() in kdump case
* Drop devm_ for adopt-time allocations; set up cleanup function via devm_add_action_or_reset()
v5
https://lore.kernel.org/all/[email protected]/
* Add Reviewed-by from Kevin
* Drop READ_ONCE on lazy-attach L1 read
* Split "Skip EVTQ/PRIQ setup" into two patches
* Tighten kdump probe comment and dev_warn message
* Use MEM + BUSY in arm_smmu_kdump_phys_is_corrupted
v4
https://lore.kernel.org/all/[email protected]/
* Rebase v7.1-rc1
* s/arm_smmu_adopt/arm_smmu_kdump_adopt
* Revert alloc/memremap/fmt on fallback
* Reorder patches to avoid bisect regression
* Use IRQ_NONE for spurious evtq/priq entries
* Cap linear log2size by kdump's allocation bound
* Defer clearing FEAT_2_LVL_STRTAB on linear adopt
* Add arm_smmu_kdump_phys_is_corrupted() validation
* Defer l2 stream table memremap till master inserts
* Re-validate L1 desc on master insert with READ_ONCE
v3
https://lore.kernel.org/all/[email protected]/
* s/OPT_KDUMP/OPT_KDUMP_ADOPT
* Do not adopt if GERROR_SFM_ERR
* Retain CR0_ATSCHK beside CR0_SMMUEN
* Clear latched GERROR bits (e.g. CMDQ_ERR)
* Assert ARM_SMMU_FEAT_COHERENCY in adopt functions
* Add STE.Cfg check in arm_smmu_is_attach_deferred()
* Fix validations on return codes from devm_memremap()
* Sanitize crashed kernel register values in adopt functions
* Drop unnecessary l2ptrs guard in arm_smmu_is_attach_deferred()
* Don't enable PRIQ/EVTQ irqs and guard the irq functions for combined irq cases
v2
https://lore.kernel.org/all/[email protected]/
* Add warning in non-coherent SMMU cases
* Keep eventq/priq disabled vs. enabling-and-disabling-later
* Check KDUMP option in the beginning of arm_smmu_device_reset()
* Validate STRTAB format matches HW capability instead of forcing flags
v1:
https://lore.kernel.org/all/[email protected]/
Nicolin Chen (9):
iommu/arm-smmu-v3: Do not enable EVTQ/PRIQ interrupts in kdump kernel iommu/arm-smmu-v3: Skip EVTQ/PRIQ setup in kdump kernel iommu/arm-smmu-v3: Add ARM_SMMU_OPT_KDUMP_ADOPT for kdump kernel iommu/arm-smmu-v3: Destroy vmid_map ida via devres iommu/arm-smmu-v3-kdump: Reserve crashed kernel's ASIDs and VMIDs iommu/arm-smmu-v3-kdump: Implement is_attach_deferred() iommu/arm-smmu-v3: Retain CR0_SMMUEN during kdump device reset iommu/arm-smmu-v3: Skip RMR bypass for kdump adoption iommu/arm-smmu-v3: Detect ARM_SMMU_OPT_KDUMP_ADOPT in probe()
drivers/iommu/arm/arm-smmu-v3/Makefile | 1 + drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h | 48 ++ .../iommu/arm/arm-smmu-v3/arm-smmu-v3-kdump.c | 579 ++++++++++++++++++ drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 246 ++++++-- 4 files changed, 806 insertions(+), 68 deletions(-) create mode 100644 drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-kdump.c
Signature · 1 line
2.43.0
PATCH v8 1/9 iommu/arm-smmu-v3: Do not enable EVTQ/PRIQ interrupts in kdump kernel
In kdump cases, the crashed kernel's CDs and page tables can be corrupted, which could trigger event spamming. Also, we cannot serve page requests.
Skip the IRQ setup for EVTQ/PRIQ in arm_smmu_setup_irqs().
Skip their IRQ handler registration in unique-IRQ and combined-IRQ cases.
Note that arm_smmu_device_reset() at this point still enables EVTQEN/PRIQEN transiently before clearing them. A following change will skip the entire queue setup, removing that transient enable window.
--- drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 58 ++++++++++++++------- 1 file changed, 39 insertions(+), 19 deletions(-)
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c +39 -19
@@ -2294,7 +2294,11 @@ static irqreturn_t arm_smmu_combined_irq_thread(int irq, void *dev)static irqreturn_t arm_smmu_combined_irq_handler (int irq,void *dev) { -arm_smmu_gerror_handler (irq, dev); +irqreturn_t ret =arm_smmu_gerror_handler (irq, dev); + +/* In kdump, EVTQ/PRIQ are disabled and there is no thread to wake */ +if (is_kdump_kernel ()) +return ret;return IRQ_WAKE_THREAD ; }
@@ -4625,6 +4629,21 @@ static void arm_smmu_setup_unique_irqs(struct arm_smmu_device *smmu)arm_smmu_setup_msis (smmu);/* Request interrupt lines */ + irq = smmu->gerr_irq; +if (irq) { + ret =devm_request_irq (smmu->dev, irq, arm_smmu_gerror_handler, +0 ,"arm-smmu-v3-gerror" , smmu); +if (ret <0 ) +dev_warn (smmu->dev,"failed to enable gerror irq\n" ); + }else { +dev_warn (smmu->dev, +"no gerr irq - errors will not be reported!\n" ); + } + +/* No EVTQ/PRIQ interrupts in kdump -- queues are disabled */ +if (is_kdump_kernel ()) +return ; + irq = smmu->evtq.q.irq;if (irq) { ret = devm_request_threaded_irq(smmu->dev, irq, NULL,
@@ -4637,16 +4656,6 @@ static void arm_smmu_setup_unique_irqs(struct arm_smmu_device *smmu)dev_warn (smmu->dev,"no evtq irq - events will not be reported!\n" ); } - irq = smmu->gerr_irq; -if (irq) { - ret =devm_request_irq (smmu->dev, irq, arm_smmu_gerror_handler, -0 ,"arm-smmu-v3-gerror" , smmu); -if (ret <0 ) -dev_warn (smmu->dev,"failed to enable gerror irq\n" ); - }else { -dev_warn (smmu->dev,"no gerr irq - errors will not be reported!\n" ); - } -if (smmu->features &ARM_SMMU_FEAT_PRI ) { irq = smmu->priq.q.irq;if (irq) {
@@ -4667,7 +4676,7 @@ static void arm_smmu_setup_unique_irqs(struct arm_smmu_device *smmu)static int arm_smmu_setup_irqs (struct arm_smmu_device *smmu) {int ret, irq; -u32 irqen_flags =IRQ_CTRL_EVTQ_IRQEN |IRQ_CTRL_GERROR_IRQEN ; +u32 irqen_flags =IRQ_CTRL_GERROR_IRQEN ;/* Disable IRQs first */ ret = arm_smmu_write_reg_sync(smmu, 0, ARM_SMMU_IRQ_CTRL,
@@ -4682,19 +4691,30 @@ static int arm_smmu_setup_irqs(struct arm_smmu_device *smmu)/* * Cavium ThunderX2 implementation doesn't support unique irq * lines. Use a single irq line for all the SMMUv3 interrupts. +* +* In kdump, EVTQ/PRIQ are disabled, so no threaded handling. */ - ret =devm_request_threaded_irq (smmu->dev, irq, - arm_smmu_combined_irq_handler, - arm_smmu_combined_irq_thread, -IRQF_ONESHOT , -"arm-smmu-v3-combined-irq" , smmu); +if (is_kdump_kernel ()) + ret =devm_request_irq (smmu->dev, irq, + arm_smmu_combined_irq_handler,0 , +"arm-smmu-v3-combined-irq" , + smmu); +else + ret =devm_request_threaded_irq ( + smmu->dev, irq, arm_smmu_combined_irq_handler, + arm_smmu_combined_irq_thread,IRQF_ONESHOT , +"arm-smmu-v3-combined-irq" , smmu);if (ret <0 )dev_warn (smmu->dev,"failed to enable combined irq\n" ); }else arm_smmu_setup_unique_irqs (smmu); -if (smmu->features &ARM_SMMU_FEAT_PRI ) - irqen_flags |=IRQ_CTRL_PRIQ_IRQEN ; +/* No EVTQ/PRIQ IRQ generation in kdump -- queues are disabled */ +if (!is_kdump_kernel ()) { + irqen_flags |=IRQ_CTRL_EVTQ_IRQEN ; +if (smmu->features &ARM_SMMU_FEAT_PRI ) + irqen_flags |=IRQ_CTRL_PRIQ_IRQEN ; + }/* Enable interrupt generation on the SMMU */ ret = arm_smmu_write_reg_sync(smmu, irqen_flags,
Signature · 1 line
2.43.0
PATCH v8 2/9 iommu/arm-smmu-v3: Skip EVTQ/PRIQ setup in kdump kernel
In reply to Nicolin ChenIn kdump cases, the crashed kernel's CDs and page tables can be corrupted, which could trigger event spamming. Also, we cannot serve page requests.
Skip the EVTQ/PRIQ setup entirely rather than enabling then disabling them.
Keep the queue allocations themselves, as their Q_MAX_SZ_SHIFT-capped sizes are negligible against a crashkernel reservation.
Also add some inline comments explaining that.
--- drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 44 +++++++++++++-------- 1 file changed, 28 insertions(+), 16 deletions(-)
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c +28 -16
@@ -4821,21 +4821,36 @@ static int arm_smmu_device_reset(struct arm_smmu_device *smmu)arm_smmu_cmdq_issue_cmd_with_sync ( smmu,arm_smmu_make_cmd_op (CMDQ_OP_TLBI_NSNH_ALL )); -/* Event queue */ -writeq_relaxed (smmu->evtq.q.q_base, smmu->base +ARM_SMMU_EVTQ_BASE ); -writel_relaxed (smmu->evtq.q.llq.prod, smmu->page1 +ARM_SMMU_EVTQ_PROD ); -writel_relaxed (smmu->evtq.q.llq.cons, smmu->page1 +ARM_SMMU_EVTQ_CONS ); - - enables |=CR0_EVTQEN ; - ret =arm_smmu_write_reg_sync (smmu, enables,ARM_SMMU_CR0 , -ARM_SMMU_CR0ACK ); -if (ret) { -dev_err (smmu->dev,"failed to enable event queue\n" ); -return ret; +/* +* Event queue +* +* Do not enable in a kdump case, as the crashed kernel's CDs and page +* tables might be corrupted, triggering event spamming. A disabled +* queue simply discards new events, without raising any global error. +*/ +if (!is_kdump_kernel ()) { +writeq_relaxed (smmu->evtq.q.q_base, + smmu->base +ARM_SMMU_EVTQ_BASE ); +writel_relaxed (smmu->evtq.q.llq.prod, + smmu->page1 +ARM_SMMU_EVTQ_PROD ); +writel_relaxed (smmu->evtq.q.llq.cons, + smmu->page1 +ARM_SMMU_EVTQ_CONS ); + + enables |=CR0_EVTQEN ; + ret =arm_smmu_write_reg_sync (smmu, enables,ARM_SMMU_CR0 , +ARM_SMMU_CR0ACK ); +if (ret) { +dev_err (smmu->dev,"failed to enable event queue\n" ); +return ret; + } } -/* PRI queue */ -if (smmu->features &ARM_SMMU_FEAT_PRI ) { +/* +* PRI queue +* +* Do not enable in a kdump case, as we cannot serve page requests. +*/ +if (!is_kdump_kernel () && (smmu->features &ARM_SMMU_FEAT_PRI )) {writeq_relaxed (smmu->priq.q.q_base, smmu->base +ARM_SMMU_PRIQ_BASE ); writel_relaxed(smmu->priq.q.llq.prod,
@@ -4868,9 +4883,6 @@ static int arm_smmu_device_reset(struct arm_smmu_device *smmu)return ret; } -if (is_kdump_kernel ()) - enables &= ~(CR0_EVTQEN |CR0_PRIQEN ); -/* Enable the SMMU interface */ enables |=CR0_SMMUEN ; ret = arm_smmu_write_reg_sync(smmu, enables, ARM_SMMU_CR0,
Signature · 1 line
2.43.0
PATCH v8 3/9 iommu/arm-smmu-v3: Add ARM_SMMU_OPT_KDUMP_ADOPT for kdump kernel
In reply to Nicolin ChenWhen transitioning to a kdump kernel, the primary kernel might have crashed while endpoint devices were actively bus-mastering DMA. Currently, the SMMU driver aggressively resets the hardware during probe by clearing CR0_SMMUEN and setting the Global Bypass Attribute (GBPA) to ABORT.
In a kdump scenario, this aggressive reset is highly destructive:
a) If GBPA is set to ABORT, in-flight DMA will be aborted, generating fatal PCIe AER or SErrors that may panic the kdump kernel
b) If GBPA is set to BYPASS, in-flight DMA targeting some IOVAs will bypass the SMMU and corrupt the physical memory at those 1:1 mapped IOVAs.
To safely absorb in-flight DMAs, a kdump kernel will have to leave SMMUEN=1 intact and avoid modifying STRTAB_BASE, allowing HW to continue translating in-flight DMAs reusing the crashed kernel's page tables until the endpoint device drivers probe and quiesce their respective hardware.
However, the ARM SMMUv3 architecture specification states that updating the SMMU_STRTAB_BASE register while SMMUEN == 1 is UNPREDICTABLE or ignored.
This leaves a kdump kernel no choice but to adopt the stream table from the crashed kernel.
Introduce ARM_SMMU_OPT_KDUMP_ADOPT and adopt functions memremapping all the stream tables extracted from STRTAB_BASE and STRTAB_BASE_CFG. Add them in a new arm-smmu-v3-kdump.c, which is only built when CONFIG_CRASH_DUMP is enabled.
Note that the adoption of the crashed kernel's stream table follows certain strict rules, since the old stream table might be compromised. Thus, apply some basic validations against the values read from the registers. If tests fail, it means the stream table cannot be trusted, so toss it entirely. To avoid OOM due to a potentially corrupted stream table, the memremap for l2 tables is done on the kdump kernel's demand.
The new option will be set in a following change, once the device reset and the RMR setup are reworked not to overwrite the adopted stream table, and the crashed kernel's in-use ASIDs and VMIDs are reserved.
--- drivers/iommu/arm/arm-smmu-v3/Makefile | 1 + drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h | 21 ++ .../iommu/arm/arm-smmu-v3/arm-smmu-v3-kdump.c | 279 ++++++++++++++++++ drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 22 +- 4 files changed, 320 insertions(+), 3 deletions(-) create mode 100644 drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-kdump.c
drivers/iommu/arm/arm-smmu-v3/Makefile +1 -0
@@ -3,6 +3,7 @@ obj-$(CONFIG_ARM_SMMU_V3) += arm_smmu_v3.o arm_smmu_v3-y := arm-smmu-v3.o arm_smmu_v3-$(CONFIG_ARM_SMMU_V3_IOMMUFD) += arm-smmu-v3-iommufd.o arm_smmu_v3-$(CONFIG_ARM_SMMU_V3_SVA) += arm-smmu-v3-sva.o +arm_smmu_v3-$(CONFIG_CRASH_DUMP) += arm-smmu-v3-kdump.o arm_smmu_v3-$(CONFIG_TEGRA241_CMDQV) += tegra241-cmdqv.o obj-$(CONFIG_ARM_SMMU_V3_KUNIT_TEST) += arm-smmu-v3-test.o
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h +21 -0
@@ -928,6 +928,7 @@ struct arm_smmu_device {#define ARM_SMMU_OPT_MSIPOLL (1 << 2)#define ARM_SMMU_OPT_CMDQ_FORCE_SYNC (1 << 3)#define ARM_SMMU_OPT_TEGRA241_CMDQV (1 << 4) +#define ARM_SMMU_OPT_KDUMP_ADOPT (1 << 5)u32 options;struct arm_smmu_cmdq cmdq;
@@ -1239,6 +1240,26 @@ tegra241_cmdqv_probe(struct arm_smmu_device *smmu) }#endif /* CONFIG_TEGRA241_CMDQV */ +#ifdef CONFIG_CRASH_DUMP +int arm_smmu_kdump_adopt_strtab (struct arm_smmu_device *smmu); +int arm_smmu_kdump_adopt_deferred_l2_strtab (struct arm_smmu_device *smmu, +u32 sid,phys_addr_t base,u32 span, +struct arm_smmu_strtab_l2 **l2table); +#else /* CONFIG_CRASH_DUMP */ +static inline int arm_smmu_kdump_adopt_strtab (struct arm_smmu_device *smmu) +{ +return -EOPNOTSUPP ; +} + +static inline int +arm_smmu_kdump_adopt_deferred_l2_strtab (struct arm_smmu_device *smmu,u32 sid, +phys_addr_t base,u32 span, +struct arm_smmu_strtab_l2 **l2table) +{ +return -EOPNOTSUPP ; +} +#endif /* CONFIG_CRASH_DUMP */ +struct arm_vsmmu {struct iommufd_viommu core;struct arm_smmu_device *smmu;
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-kdump.c new file +279 -0
279 lines not on this page · raw message
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c +19 -3
@@ -1938,11 +1938,23 @@ static int arm_smmu_init_l2_strtab(struct arm_smmu_device *smmu, u32 sid)dma_addr_t l2ptr_dma;struct arm_smmu_strtab_cfg *cfg = &smmu->strtab_cfg;struct arm_smmu_strtab_l2 **l2table; +u32 l1_idx =arm_smmu_strtab_l1_idx (sid); - l2table = &cfg->l2.l2ptrs[arm_smmu_strtab_l1_idx (sid)]; + l2table = &cfg->l2.l2ptrs[l1_idx];if (*l2table)return 0 ; +/* Deferred adoption of the crashed kernel's L2 table */ +if (smmu->options &ARM_SMMU_OPT_KDUMP_ADOPT ) { +u64 l2ptr =le64_to_cpu (cfg->l2.l1tab[l1_idx].l2ptr); +phys_addr_t base = l2ptr &STRTAB_L1_DESC_L2PTR_MASK ; +u32 span =FIELD_GET (STRTAB_L1_DESC_SPAN , l2ptr); + +if (span) +return arm_smmu_kdump_adopt_deferred_l2_strtab ( + smmu, sid, base, span, l2table); + } + *l2table =dmam_alloc_coherent (smmu->dev,sizeof (**l2table), &l2ptr_dma,GFP_KERNEL );if (!*l2table) {
@@ -1954,8 +1966,7 @@ static int arm_smmu_init_l2_strtab(struct arm_smmu_device *smmu, u32 sid)arm_smmu_init_initial_stes ((*l2table)->stes,ARRAY_SIZE ((*l2table)->stes)); -arm_smmu_write_strtab_l1_desc (&cfg->l2.l1tab[arm_smmu_strtab_l1_idx (sid)], - l2ptr_dma); +arm_smmu_write_strtab_l1_desc (&cfg->l2.l1tab[l1_idx], l2ptr_dma);return 0 ; }
@@ -4498,6 +4509,10 @@ static int arm_smmu_init_strtab(struct arm_smmu_device *smmu) {int ret; +if ((smmu->options &ARM_SMMU_OPT_KDUMP_ADOPT ) && + !arm_smmu_kdump_adopt_strtab (smmu)) + goto out; +if (smmu->features &ARM_SMMU_FEAT_2_LVL_STRTAB ) ret =arm_smmu_init_strtab_2lvl (smmu);else
@@ -4505,6 +4520,7 @@ static int arm_smmu_init_strtab(struct arm_smmu_device *smmu)if (ret)return ret; +out:ida_init (&smmu->vmid_map);return 0 ;
Signature · 1 line
2.43.0
PATCH v8 4/9 iommu/arm-smmu-v3: Destroy vmid_map ida via devres
In reply to Nicolin ChenThe vmid_map ida is only destroyed in arm_smmu_device_remove(), which does not run when the probe fails. This is currently harmless, as the ida stays empty until the first S2 domain allocation, which can only happen after a successful probe.
An upcoming change will start reserving the crashed kernel's VMIDs in this ida, at the probe time of a kdump kernel. A probe failure would then leak the ida's internal allocations.
Register a devres action right after ida_init(), making devres the single owner that covers both the unbind and probe failure paths.
--- drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-)
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c +9 -2
@@ -4505,6 +4505,13 @@ static int arm_smmu_init_strtab_linear(struct arm_smmu_device *smmu)return 0 ; } +static void arm_smmu_deinit_strtab (void *data) +{ +struct arm_smmu_device *smmu = data; + +ida_destroy (&smmu->vmid_map); +} +static int arm_smmu_init_strtab (struct arm_smmu_device *smmu) {int ret;
@@ -4523,7 +4530,8 @@ static int arm_smmu_init_strtab(struct arm_smmu_device *smmu) out:ida_init (&smmu->vmid_map); -return 0 ; +return devm_add_action_or_reset (smmu->dev, arm_smmu_deinit_strtab, + smmu); }static int arm_smmu_init_structures (struct arm_smmu_device *smmu)
@@ -5564,7 +5572,6 @@ static void arm_smmu_device_remove(struct platform_device *pdev)iommu_device_sysfs_remove (&smmu->iommu);arm_smmu_device_disable (smmu);iopf_queue_free (smmu->evtq.iopf); -ida_destroy (&smmu->vmid_map); }static void arm_smmu_device_shutdown (struct platform_device *pdev)
Signature · 1 line
2.43.0
PATCH v8 5/9 iommu/arm-smmu-v3-kdump: Reserve crashed kernel's ASIDs and VMIDs
In reply to Nicolin ChenThe adopted stream table keeps translating in-flight DMA, so the SMMU keeps caching TLB entries tagged with the crashed kernel's ASIDs and VMIDs. If this kernel handed one of those IDs to its own domain, the new domain's DMA could hit the crashed kernel's cached translations, e.g. a stale entry left behind by an invalidation that the crash cut short.
Scan the adopted stream table at adoption time and reserve every ID in use:
- Walk the STEs, transiently memremapping each L2 table
- Reserve the S2VMID of S2 and nested STEs in the vmid ida
- Walk the CD tables of S1 STEs (linear and 2-level formats), reserving the ASIDs in the asid xarray.
Nested STE's guest-owned CD table is in IPA space and left alone: its ASIDs only pair with the nonzero S2VMID being reserved, so they cannot alias this kernel's VMID-0 or EL2 stage-1 domains.
The scan walks untrusted tables, yet every loop is strictly index-bounded:
the iteration counts derive from the log2size and s1cdmax fields, which are validated against this kernel's own sid_bits and ssid_bits, so a corrupted table cannot extend the walk.
Since both kernels allocate ASIDs from 1, reserving any in-use ASID would often conflict with another adopting SMMU or with a live domain. So, store a per-scan ID as an xarray value entry: a conflict against a value entry is just a safe dedup, as all the reservations are permanent, while one against a pointer entry, i.e. a live domain that will soon free its ASID for reuse, has to toss the entire adoption. The scan ID also scopes a failing scan's rollback to exactly the entries that it inserted, so a rollback can never erase any committed reservation.
Note that, on an E2H/VHE host, the kernel's stage-1 domains are tagged by the EL2 ASID, and the TLBI_EL2_* commands take no VMID. So isolating this kernel by a reserved VMID alone would not work. Reserving the ASIDs covers both the E2H and the NSEL1 cases.
Reservations are never released: a kdump kernel reboots after it saves the vmcore, and the full-reset fallback flushes the entire TLB, which turns any stale reservation into a merely unused ID.
If the scan finds any inconsistent structure, toss the entire adoption and fall back to the full reset.
Also, a successful scan makes arm_smmu_init_strtab() return early, leaving the DMA addresses of the stream table unset; a following change will guard arm_smmu_write_strtab() in arm_smmu_device_reset().
--- .../iommu/arm/arm-smmu-v3/arm-smmu-v3-kdump.c | 268 +++++++++++++++++- drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 17 +- 2 files changed, 269 insertions(+), 16 deletions(-)
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-kdump.c +261 -7
@@ -32,6 +32,247 @@#include "arm-smmu-v3.h" +/* +* Commit or roll back an entire scan atomically, so that a concurrently +* probing SMMU (e.g. forced by driver_async_probe) can only dedup against +* the reservations that will persist +*/ +static DEFINE_MUTEX (arm_smmu_kdump_resv_lock); + +/* Identifies the current scan's reservations; serialized by the lock above */ +static unsigned long arm_smmu_kdump_scan_id; + +/* +* The adopted stream table keeps translating in-flight DMAs, so the SMMU also +* keeps caching TLB entries tagged with the crashed kernel's ASIDs and VMIDs. +* Reserve all the in-use IDs, so that this kernel cannot give its own domains +* an overlapping ID that would alias the crashed kernel's TLB entries. +* +* The reservations are only released when the entire adoption is tossed, as +* the full-reset fallback flushes the entire TLB. Otherwise, they are kept +* for the lifetime of the kdump kernel, which reboots after saving a vmcore. +*/ +static int arm_smmu_kdump_resv_asid (struct arm_smmu_device *smmu,u32 asid) +{ +int ret; + +/* A valid CD never has ASID 0; both kernels share the same HW limit */ +if (!asid || asid >=1UL << smmu->asid_bits) +return -EINVAL ; + +guard (mutex)(&arm_smmu_asid_lock); + +/* The value entry marks the ASID as in-use and identifies its scan */ + ret =xa_insert (&arm_smmu_asid_xa, asid, +xa_mk_value (arm_smmu_kdump_scan_id),GFP_KERNEL ); +/* +* An -EBUSY against a value entry is just a safe dedup against another +* permanent reservation. A pointer entry means a live domain that will +* free its ASID for reuse eventually: keep -EBUSY to toss the adoption. +*/ +if (ret == -EBUSY &&xa_is_value (xa_load (&arm_smmu_asid_xa, asid))) + ret =0 ; +return ret; +} + +static int arm_smmu_kdump_resv_vmid (struct arm_smmu_device *smmu,u32 vmid) +{ +int ret; + +/* A translating STE never has VMID 0, which is reserved for bypass */ +if (!vmid || vmid >=1UL << smmu->vmid_bits) +return -EINVAL ; + + ret =ida_alloc_range (&smmu->vmid_map, vmid, vmid,GFP_KERNEL ); +if (ret <0 && ret != -ENOSPC )/* -ENOSPC means already reserved */ +return ret; +return 0 ; +} + +static int arm_smmu_kdump_resv_cd_asids (struct arm_smmu_device *smmu, +struct arm_smmu_cd *cds,u32 num_cds) +{ +int ret =0 ; +u32 i; + +for (i =0 ; i < num_cds; i++) { +u64 val =le64_to_cpu (cds[i].data[0 ]); +u32 asid =FIELD_GET (CTXDESC_CD_0_ASID , val); + +if (!(val &CTXDESC_CD_0_V )) +continue ; + ret =arm_smmu_kdump_resv_asid (smmu, asid); +if (ret) +break ; + } +return ret; +} + +static int arm_smmu_kdump_resv_s1_asids (struct arm_smmu_device *smmu,u64 ste0) +{ +phys_addr_t cdtab = ste0 &STRTAB_STE_0_S1CTXPTR_MASK ; +u32 s1cdmax =FIELD_GET (STRTAB_STE_0_S1CDMAX , ste0); +u32 s1fmt =FIELD_GET (STRTAB_STE_0_S1FMT , ste0); +size_t max_contexts =1UL << s1cdmax; +struct arm_smmu_cdtab_l1 *l1tab; +u32 num_l1_ents, num_cds, i; +int ret =0 ; + +if (!cdtab || s1cdmax > smmu->ssid_bits) +return -EINVAL ; + +if (s1fmt ==STRTAB_STE_0_S1FMT_LINEAR ) { +struct arm_smmu_cd *cds; + +/* +* A crashed kernel might have used a linear CD table on the +* 2-level capable hardware like the linear stream table case. +* So, accept it here as well. s1cdmax is capped by ssid_bits. +*/ + cds =memremap (cdtab, max_contexts *sizeof (*cds),MEMREMAP_WB ); +if (!cds) +return -ENOMEM ; + ret =arm_smmu_kdump_resv_cd_asids (smmu, cds, max_contexts); +memunmap (cds); +return ret; + } + +if (s1fmt !=STRTAB_STE_0_S1FMT_64K_L2 ) +return -EINVAL ; + + num_l1_ents =DIV_ROUND_UP (max_contexts,CTXDESC_L2_ENTRIES ); + l1tab =memremap (cdtab, num_l1_ents *sizeof (*l1tab),MEMREMAP_WB ); +if (!l1tab) +return -ENOMEM ; + +/* max_contexts being under a full leaf makes the only leaf partial */ + num_cds =min_t (size_t, max_contexts,CTXDESC_L2_ENTRIES ); + +/* Aliased L2 tables cannot extend the walk; they only repeat a scan */ +for (i =0 ; i < num_l1_ents; i++) { +u64 l1_desc =le64_to_cpu (l1tab[i].l2ptr); +struct arm_smmu_cdtab_l2 *l2; + +if (!(l1_desc &CTXDESC_L1_DESC_V )) +continue ; + + l2 =memremap (l1_desc &CTXDESC_L1_DESC_L2PTR_MASK , + num_cds *sizeof (*l2->cds),MEMREMAP_WB ); +if (!l2) { + ret = -ENOMEM ; +break ; + } + ret =arm_smmu_kdump_resv_cd_asids (smmu, l2->cds, num_cds); +memunmap (l2); +if (ret) +break ; + } +memunmap (l1tab); +return ret; +} + +static int arm_smmu_kdump_resv_ste_ids (struct arm_smmu_device *smmu, +struct arm_smmu_ste *ste) +{ +u32 vmid =FIELD_GET (STRTAB_STE_2_S2VMID ,le64_to_cpu (ste->data[2 ])); +u64 val =le64_to_cpu (ste->data[0 ]); + +if (!(val &STRTAB_STE_0_V )) +return 0 ; + +switch (FIELD_GET (STRTAB_STE_0_CFG , val)) { +case STRTAB_STE_0_CFG_ABORT : +case STRTAB_STE_0_CFG_BYPASS : +return 0 ; +case STRTAB_STE_0_CFG_S1_TRANS : +return arm_smmu_kdump_resv_s1_asids (smmu, val); +case STRTAB_STE_0_CFG_NESTED : +/* +* A guest-owned CD table is in IPA space, unreachable. Its +* ASIDs are only tagged with the S2VMID reserved below, so +* they cannot alias this kernel's VMID-0 or EL2 S1 domains. +*/ + fallthrough; +case STRTAB_STE_0_CFG_S2_TRANS : +return arm_smmu_kdump_resv_vmid (smmu, vmid); +default : +return -EINVAL ; + } +} + +static int arm_smmu_kdump_resv_ids (struct arm_smmu_device *smmu) +{ +struct arm_smmu_strtab_cfg *cfg = &smmu->strtab_cfg; +int ret =0 ; +u32 i, j; + +lockdep_assert_held (&arm_smmu_kdump_resv_lock); + +/* Allocate a new ID for this scan, to scope its rollback */ + arm_smmu_kdump_scan_id++; + +if (!(smmu->features &ARM_SMMU_FEAT_2_LVL_STRTAB )) { +for (i =0 ; i < cfg->linear.num_ents; i++) { + ret =arm_smmu_kdump_resv_ste_ids ( + smmu, &cfg->linear.table[i]); +if (ret) +return ret; + } +return 0 ; + } + +/* Aliased L2 tables cannot extend the walk; they only repeat a scan */ +for (i =0 ; i < cfg->l2.num_l1_ents; i++) { +u64 l1_desc =le64_to_cpu (cfg->l2.l1tab[i].l2ptr); +phys_addr_t base = l1_desc &STRTAB_L1_DESC_L2PTR_MASK ; +u32 span =FIELD_GET (STRTAB_L1_DESC_SPAN , l1_desc); +struct arm_smmu_strtab_l2 *l2; + +if (!span) +continue ; + +/* Validated at adopt time, so a change means live corruption */ +if (span !=STRTAB_SPLIT +1 || !base) +return -EINVAL ; + +/* Transient map: L2 tables are only adopted upon device use */ + l2 =memremap (base,sizeof (*l2),MEMREMAP_WB ); +if (!l2) +return -ENOMEM ; +for (j =0 ; j <ARRAY_SIZE (l2->stes); j++) { + ret =arm_smmu_kdump_resv_ste_ids (smmu, &l2->stes[j]); +if (ret) +break ; + } +memunmap (l2); +if (ret) +return ret; + } +return 0 ; +} + +/* +* Roll back a scan that has not committed yet. Committed reservations are +* never released, as another SMMU's scan might have deduped against them. +*/ +static void arm_smmu_kdump_unresv_ids (struct arm_smmu_device *smmu) +{ +unsigned long index; +void *entry; + +lockdep_assert_held (&arm_smmu_kdump_resv_lock); + +mutex_lock (&arm_smmu_asid_lock); +xa_for_each (&arm_smmu_asid_xa, index, entry) { +if (entry ==xa_mk_value (arm_smmu_kdump_scan_id)) +xa_erase (&arm_smmu_asid_xa, index); + } +mutex_unlock (&arm_smmu_asid_lock); + +/* No domain exists yet, so the ida holds only the reservations */ +ida_destroy (&smmu->vmid_map); +} +int arm_smmu_kdump_adopt_deferred_l2_strtab (struct arm_smmu_device *smmu,u32 sid,phys_addr_t base,u32 span,struct arm_smmu_strtab_l2 **l2table)
@@ -255,24 +496,37 @@ int arm_smmu_kdump_adopt_strtab(struct arm_smmu_device *smmu) goto err; } +mutex_lock (&arm_smmu_kdump_resv_lock); + ret =arm_smmu_kdump_resv_ids (smmu); +if (ret) { +dev_warn (smmu->dev,"failed to reserve in-use ASIDs/VMIDs\n" ); +arm_smmu_kdump_adopt_cleanup (smmu); + goto err_unresv; + } + ret =devm_add_action_or_reset (smmu->dev, arm_smmu_kdump_adopt_cleanup, smmu);/* devm_add_action_or_reset ran the cleanup upon failure */ if (ret) {dev_warn (smmu->dev,"failed to set up cleanup action\n" ); -/* -* Undo the linear adoption's clearing of FEAT_2_LVL_STRTAB so -* the full-reset fallback uses the hardware-supported format. -*/ -if (was_2lvl) - smmu->features |=ARM_SMMU_FEAT_2_LVL_STRTAB ; - goto err; + goto err_unresv; } +mutex_unlock (&arm_smmu_kdump_resv_lock);return 0 ; +err_unresv: +/* The full reset will flush the entire TLB, so release everything */ +arm_smmu_kdump_unresv_ids (smmu); +mutex_unlock (&arm_smmu_kdump_resv_lock); err:dev_warn (smmu->dev,"falling back to full reset\n" ); +/* +* Undo the linear adoption's clearing of FEAT_2_LVL_STRTAB so that the +* full-reset fallback uses the hardware-supported format. +*/ +if (was_2lvl) + smmu->features |=ARM_SMMU_FEAT_2_LVL_STRTAB ;memset (&smmu->strtab_cfg,0 ,sizeof (smmu->strtab_cfg)); smmu->options &= ~ARM_SMMU_OPT_KDUMP_ADOPT ;return ret;
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c +8 -9
@@ -4516,22 +4516,21 @@ static int arm_smmu_init_strtab(struct arm_smmu_device *smmu) {int ret; +/* Init first, as a kdump adoption reserves in-use VMIDs in the ida */ +ida_init (&smmu->vmid_map); + ret =devm_add_action_or_reset (smmu->dev, arm_smmu_deinit_strtab, smmu); +if (ret) +return ret; +if ((smmu->options &ARM_SMMU_OPT_KDUMP_ADOPT ) && !arm_smmu_kdump_adopt_strtab (smmu)) - goto out; +return 0 ;if (smmu->features &ARM_SMMU_FEAT_2_LVL_STRTAB ) ret =arm_smmu_init_strtab_2lvl (smmu);else ret =arm_smmu_init_strtab_linear (smmu); -if (ret) -return ret; - -out: -ida_init (&smmu->vmid_map); - -return devm_add_action_or_reset (smmu->dev, arm_smmu_deinit_strtab, - smmu); +return ret; }static int arm_smmu_init_structures (struct arm_smmu_device *smmu)
Signature · 1 line
2.43.0
PATCH v8 6/9 iommu/arm-smmu-v3-kdump: Implement is_attach_deferred()
In reply to Nicolin ChenThough the kdump kernel adopts the crashed kernel's stream table, the iommu core will still try to attach each probed device to a default domain, which overwrites the adopted STE and breaks in-flight DMA from that device.
Implement an is_attach_deferred() callback to prevent this. For each device that has STE.V=1 and STE.Cfg!=Abort in the adopted table, defer the default domain attachment, until the device driver explicitly requests it.
Also, move arm_smmu_get_step_for_sid() to the header for the kdump function to use.
--- drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h | 22 ++++++++++++++++ .../iommu/arm/arm-smmu-v3/arm-smmu-v3-kdump.c | 19 ++++++++++++++ drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 25 ++++++++----------- 3 files changed, 51 insertions(+), 15 deletions(-)
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h +22 -0
@@ -1208,6 +1208,21 @@ void arm_smmu_attach_commit(struct arm_smmu_attach_state *state);void arm_smmu_install_ste_for_dev (struct arm_smmu_master *master,const struct arm_smmu_ste *target); +static inline struct arm_smmu_ste * +arm_smmu_get_step_for_sid (struct arm_smmu_device *smmu,u32 sid) +{ +struct arm_smmu_strtab_cfg *cfg = &smmu->strtab_cfg; + +if (smmu->features &ARM_SMMU_FEAT_2_LVL_STRTAB ) { +/* Two-level walk */ +return &cfg->l2.l2ptrs[arm_smmu_strtab_l1_idx (sid)] + ->stes[arm_smmu_strtab_l2_idx (sid)]; + }else { +/* Simple linear lookup */ +return &cfg->linear.table[sid]; + } +} + int arm_smmu_cmdq_issue_cmdlist(struct arm_smmu_device *smmu, struct arm_smmu_cmdq *cmdq, struct arm_smmu_cmd *cmds, int n,
@@ -1245,6 +1260,7 @@ int arm_smmu_kdump_adopt_strtab(struct arm_smmu_device *smmu);int arm_smmu_kdump_adopt_deferred_l2_strtab (struct arm_smmu_device *smmu,u32 sid,phys_addr_t base,u32 span,struct arm_smmu_strtab_l2 **l2table); +bool arm_smmu_kdump_is_attach_deferred (struct arm_smmu_master *master);#else /* CONFIG_CRASH_DUMP */ static inline int arm_smmu_kdump_adopt_strtab (struct arm_smmu_device *smmu) {
@@ -1258,6 +1274,12 @@ arm_smmu_kdump_adopt_deferred_l2_strtab(struct arm_smmu_device *smmu, u32 sid, {return -EOPNOTSUPP ; } + +static inline bool +arm_smmu_kdump_is_attach_deferred (struct arm_smmu_master *master) +{ +return false; +}#endif /* CONFIG_CRASH_DUMP */ struct arm_vsmmu {
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-kdump.c +19 -0
@@ -531,3 +531,22 @@ int arm_smmu_kdump_adopt_strtab(struct arm_smmu_device *smmu) smmu->options &= ~ARM_SMMU_OPT_KDUMP_ADOPT ;return ret; } + +bool arm_smmu_kdump_is_attach_deferred (struct arm_smmu_master *master) +{ +struct arm_smmu_device *smmu = master->smmu; +int i; + +for (i =0 ; i < master->num_streams; i++) { +struct arm_smmu_ste *ste = +arm_smmu_get_step_for_sid (smmu, master->streams[i].id); +u64 ent0 =le64_to_cpu (ste->data[0 ]); + +/* Defer only when there might be in-flight DMAs */ +if ((ent0 &STRTAB_STE_0_V ) && +FIELD_GET (STRTAB_STE_0_CFG , ent0) !=STRTAB_STE_0_CFG_ABORT ) +return true; + } + +return false; +}
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c +10 -15
@@ -2898,21 +2898,6 @@ static int arm_smmu_domain_finalise(struct arm_smmu_domain *smmu_domain,return 0 ; } -static struct arm_smmu_ste * -arm_smmu_get_step_for_sid (struct arm_smmu_device *smmu,u32 sid) -{ -struct arm_smmu_strtab_cfg *cfg = &smmu->strtab_cfg; - -if (smmu->features &ARM_SMMU_FEAT_2_LVL_STRTAB ) { -/* Two-level walk */ -return &cfg->l2.l2ptrs[arm_smmu_strtab_l1_idx (sid)] - ->stes[arm_smmu_strtab_l2_idx (sid)]; - }else { -/* Simple linear lookup */ -return &cfg->linear.table[sid]; - } -} -void arm_smmu_install_ste_for_dev (struct arm_smmu_master *master,const struct arm_smmu_ste *target) {
@@ -4318,6 +4303,15 @@ static int arm_smmu_def_domain_type(struct device *dev)return 0 ; } +static bool arm_smmu_is_attach_deferred (struct device *dev) +{ +struct arm_smmu_master *master =dev_iommu_priv_get (dev); + +if (master->smmu->options &ARM_SMMU_OPT_KDUMP_ADOPT ) +return arm_smmu_kdump_is_attach_deferred (master); +return false; +} +static const struct iommu_ops arm_smmu_ops = { .identity_domain = &arm_smmu_identity_domain, .blocked_domain = &arm_smmu_blocked_domain,
@@ -4326,6 +4320,7 @@ static const struct iommu_ops arm_smmu_ops = { .hw_info = arm_smmu_hw_info, .domain_alloc_sva = arm_smmu_sva_domain_alloc, .domain_alloc_paging_flags = arm_smmu_domain_alloc_paging_flags, + .is_attach_deferred = arm_smmu_is_attach_deferred, .probe_device = arm_smmu_probe_device, .release_device = arm_smmu_release_device, .device_group = arm_smmu_device_group,
Signature · 1 line
2.43.0
PATCH v8 7/9 iommu/arm-smmu-v3: Retain CR0_SMMUEN during kdump device reset
In reply to Nicolin ChenWhen ARM_SMMU_OPT_KDUMP_ADOPT is detected, do not disable SMMUEN and skip the CR1/CR2/STRTAB_BASE update sequence in arm_smmu_device_reset(). Those register writes are all CONSTRAINED UNPREDICTABLE while CR0_SMMUEN==1, so leaving them intact lets in-flight DMAs continue to be translated by the adopted stream table.
Initialize 'enables' to 0, so it can carry the retained CR0 fields in the kdump case, clearing only the queue enable bits. Then, preserve them when enabling the command queue.
Clear latched gerror bits if necessary.
--- drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 60 +++++++++++++++++++-- 1 file changed, 56 insertions(+), 4 deletions(-)
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c +56 -4
@@ -4781,10 +4781,28 @@ static void arm_smmu_write_strtab(struct arm_smmu_device *smmu)static int arm_smmu_device_reset (struct arm_smmu_device *smmu) {int ret; -u32 reg, enables; +u32 reg, enables =0 ; -/* Clear CR0 and sync (disables SMMU and queue processing) */ reg =readl_relaxed (smmu->base +ARM_SMMU_CR0 ); + +/* +* In a kdump case (set when CR0_SMMUEN=1 and !GERROR_SFM_ERR), retain +* all the live CR0 fields, e.g. CR0_SMMUEN to avoid aborting in-flight +* DMA and CR0_ATSCHK to carry on the ATS-check policy, while clearing +* only the queue enable bits for this kernel to take over the queues. +* +* According to spec, updating STRTAB_BASE/CR1/CR2 when CR0_SMMUEN=1 is +* CONSTRAINED UNPREDICTABLE. So, skip those register updates and rely +* on the adopted stream table from the crashed kernel. +*/ +if (smmu->options &ARM_SMMU_OPT_KDUMP_ADOPT ) { +dev_info (smmu->dev, +"kdump: retaining SMMUEN for in-flight DMA\n" ); + enables = reg & ~(CR0_CMDQEN |CR0_EVTQEN |CR0_PRIQEN ); + goto reset_queues; + } + +/* Clear CR0 and sync (disables SMMU and queue processing) */ if (reg &CR0_SMMUEN ) {dev_warn (smmu->dev,"SMMU currently enabled! Resetting...\n" );arm_smmu_update_gbpa (smmu,GBPA_ABORT ,0 );
@@ -4814,12 +4832,41 @@ static int arm_smmu_device_reset(struct arm_smmu_device *smmu)/* Stream table */ arm_smmu_write_strtab (smmu); +reset_queues: +if (smmu->options &ARM_SMMU_OPT_KDUMP_ADOPT ) { +/* +* Disable queues since arm_smmu_device_disable() was skipped. +* CR0 fields are independent per spec, so the queue enable bits +* can be cleared while retaining SMMUEN=1. +*/ + ret =arm_smmu_write_reg_sync (smmu, enables,ARM_SMMU_CR0 , +ARM_SMMU_CR0ACK ); +if (ret) { +dev_err (smmu->dev,"failed to disable queues\n" ); +return ret; + } + } + +/* +* GERROR bits are latched. Read after queue disabling so that unhandled +* errors would be visible. Ack everything prior to re-enabling the CMDQ +* as a stale CMDQ_ERR would halt the CMDQ and new command will timeout. +* Acking SFM_ERR is defined too, although it would not exit the SFM. +*/ +if (is_kdump_kernel ()) { +u32 gerror =readl_relaxed (smmu->base +ARM_SMMU_GERROR ); +u32 gerrorn =readl_relaxed (smmu->base +ARM_SMMU_GERRORN ); + +if ((gerror ^ gerrorn) &GERROR_ERR_MASK ) +writel (gerror, smmu->base +ARM_SMMU_GERRORN ); + } +/* Command queue */ writeq_relaxed (smmu->cmdq.q.q_base, smmu->base +ARM_SMMU_CMDQ_BASE );writel_relaxed (smmu->cmdq.q.llq.prod, smmu->base +ARM_SMMU_CMDQ_PROD );writel_relaxed (smmu->cmdq.q.llq.cons, smmu->base +ARM_SMMU_CMDQ_CONS ); - enables =CR0_CMDQEN ; + enables |=CR0_CMDQEN ; ret =arm_smmu_write_reg_sync (smmu, enables,ARM_SMMU_CR0 ,ARM_SMMU_CR0ACK );if (ret) {
@@ -4885,7 +4932,12 @@ static int arm_smmu_device_reset(struct arm_smmu_device *smmu) } } -if (smmu->features &ARM_SMMU_FEAT_ATS ) { +/* +* In a kdump adopt case, retain the crashed kernel's ATS-check policy +* captured above rather than forcing it on. +*/ +if (!(smmu->options &ARM_SMMU_OPT_KDUMP_ADOPT ) && + (smmu->features &ARM_SMMU_FEAT_ATS )) { enables |=CR0_ATSCHK ; ret =arm_smmu_write_reg_sync (smmu, enables,ARM_SMMU_CR0 ,ARM_SMMU_CR0ACK );
Signature · 1 line
2.43.0
PATCH v8 8/9 iommu/arm-smmu-v3: Skip RMR bypass for kdump adoption
In reply to Nicolin ChenRMR bypass STEs are installed during SMMUv3 probe for StreamIDs listed by IORT RMR nodes. A normal boot switches the driver to a fresh stream table whose initial STEs abort, so those RMR SIDs need bypass entries before it becomes live. This preserves firmware/guest-owned traffic, including vSMMU guest MSI cases built around RMR-described SIDs.
ARM_SMMU_OPT_KDUMP_ADOPT is the opposite case: the driver keeps SMMUEN set and adopts the crashed kernel's stream table, so RMR SIDs already have the only translation state known to be safe for active in-flight DMA. Replacing an adopted STE with bypass can turn translated DMA into physical DMA, then point it at the wrong memory.
arm_smmu_make_bypass_ste() also rewrites the STE in place after clearing it first. While the table is live, a concurrent hardware STE fetch can observe V=0 or mixed old/new state.
Leaving the adopted STE unmodified keeps the kdump kernel using the crashed kernel's translation. That gives the endpoint driver a chance to probe and quiesce the device.
If the old STE was already abort or invalid, installing bypass would create new DMA permission; leaving it alone is a safer failure mode. Later domain setup still gets the RMR direct mappings through the reserved-region path.
--- drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-)
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c +9 -4
@@ -5421,6 +5421,14 @@ static void arm_smmu_rmr_install_bypass_ste(struct arm_smmu_device *smmu)struct list_head rmr_list;struct iommu_resv_region *e; +/* +* Kdump adoption keeps the crashed kernel's table live. Rewriting the +* adopted STE here could expose an in-flight fetch to a transient V=0 +* entry, or change Cfg=translate to Cfg=bypass. Must skip here. +*/ +if (smmu->options &ARM_SMMU_OPT_KDUMP_ADOPT ) +return ; +INIT_LIST_HEAD (&rmr_list);iort_get_rmr_sids (dev_fwnode (smmu->dev), &rmr_list);
@@ -5437,10 +5445,7 @@ static void arm_smmu_rmr_install_bypass_ste(struct arm_smmu_device *smmu)continue ; } -/* -* STE table is not programmed to HW, see -* arm_smmu_initial_bypass_stes() -*/ +/* The fresh stream table is not yet live. */ arm_smmu_make_bypass_ste (smmu,arm_smmu_get_step_for_sid (smmu, rmr->sids[i])); }
Signature · 1 line
2.43.0
PATCH v8 9/9 iommu/arm-smmu-v3: Detect ARM_SMMU_OPT_KDUMP_ADOPT in probe()
In reply to Nicolin Chenarm_smmu_device_hw_probe() runs before arm_smmu_init_structures(), so it's natural to decide whether the kdump kernel must adopt the crashed kernel's stream table.
Given that memremap is used to adopt the old stream table, set this option only on a coherent SMMU.
And make sure SMMU isn't in Service Failure Mode.
--- drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h | 5 ++++ .../iommu/arm/arm-smmu-v3/arm-smmu-v3-kdump.c | 27 +++++++++++++++++++ drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 4 +++ 3 files changed, 36 insertions(+)
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h +5 -0
@@ -1261,6 +1261,7 @@ int arm_smmu_kdump_adopt_deferred_l2_strtab(struct arm_smmu_device *smmu, u32 sid, phys_addr_t base, u32 span, struct arm_smmu_strtab_l2 **l2table);bool arm_smmu_kdump_is_attach_deferred (struct arm_smmu_master *master); +void arm_smmu_device_kdump_probe (struct arm_smmu_device *smmu);#else /* CONFIG_CRASH_DUMP */ static inline int arm_smmu_kdump_adopt_strtab (struct arm_smmu_device *smmu) {
@@ -1280,6 +1281,10 @@ arm_smmu_kdump_is_attach_deferred(struct arm_smmu_master *master) {return false; } + +static inline void arm_smmu_device_kdump_probe (struct arm_smmu_device *smmu) +{ +}#endif /* CONFIG_CRASH_DUMP */ struct arm_vsmmu {
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-kdump.c +27 -0
@@ -550,3 +550,30 @@ bool arm_smmu_kdump_is_attach_deferred(struct arm_smmu_master *master)return false; } + +void arm_smmu_device_kdump_probe (struct arm_smmu_device *smmu) +{ +u32 gerror, gerrorn, active; + +/* No adoption if SMMU is disabled (i.e., there is no in-flight DMA) */ +if (!(readl_relaxed (smmu->base +ARM_SMMU_CR0 ) &CR0_SMMUEN )) +return ; + +/* For now, only support a coherent SMMU that works with MEMREMAP_WB */ +if (!(smmu->features &ARM_SMMU_FEAT_COHERENCY )) { +dev_warn (smmu->dev, +"non-coherent SMMU unsupported; reset to block all DMAs\n" ); +return ; + } + + gerror =readl_relaxed (smmu->base +ARM_SMMU_GERROR ); + gerrorn =readl_relaxed (smmu->base +ARM_SMMU_GERRORN ); + active = gerror ^ gerrorn; +if (active &GERROR_SFM_ERR ) { +dev_warn (smmu->dev, +"SMMU in Service Failure Mode, must reset\n" ); +return ; + } + + smmu->options |=ARM_SMMU_OPT_KDUMP_ADOPT ; +}
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c +4 -0
@@ -5257,6 +5257,10 @@ static int arm_smmu_device_hw_probe(struct arm_smmu_device *smmu)dev_info (smmu->dev,"oas %lu-bit (features 0x%08x)\n" , smmu->oas, smmu->features); + +if (is_kdump_kernel ()) +arm_smmu_device_kdump_probe (smmu); +return 0 ; }
Signature · 1 line
2.43.0
On Fri, Jul 10, 2026 at 05:52:41PM -0700, Nicolin Chen wrote:
Hi Nicolin,
Quoted 47 lines
When transitioning to a kdump kernel, the primary kernel might have crashed while endpoint devices were actively bus-mastering DMA. Currently, the SMMU driver aggressively resets the hardware during probe by clearing
CR0_SMMUENand setting the Global Bypass Attribute (GBPA) to ABORT.In a kdump scenario, this aggressive reset is highly destructive:
a) If GBPA is set to ABORT, in-flight DMA will be aborted, generating fatal PCIe AER or SErrors that may panic the kdump kernel
b) If GBPA is set to BYPASS, in-flight DMA targeting some IOVAs will bypass the SMMU and corrupt the physical memory at those 1:1 mapped IOVAs.To safely absorb in-flight DMA, the kdump kernel must leave SMMUEN=1 intact and avoid modifying
STRTAB_BASE. This allows HW to continue translating in- flight DMA using the crashed kernel's page tables until the endpoint device drivers probe and quiesce their respective hardware.However, the ARM SMMUv3 architecture specification states that updating the
SMMU_STRTAB_BASEregister while SMMUEN == 1 is UNPREDICTABLE or ignored.This leaves a kdump kernel no choice but to adopt the stream table from the crashed kernel.
In this series:
- Introduce anARM_SMMU_OPT_KDUMP_ADOPT
- Skip SMMUEN andSTRTAB_BASEresets inarm_smmu_device_reset()
- Skip EVENTQ/PRIQ setup including interrupts and their handlers
- Memremap the crashed kernel's stream tables into the kdump kernel [*]
- Reserve the crashed kernel's in-use ASIDs and VMIDs, preventing any TLB aliasing with the kdump kernel's own domains
- Defer any default domain attachment to retain STEs until device drivers explicitly request it.
Most of the kdump code is added to a newarm-smmu-v3-kdump.cthat is only built whenCONFIG_CRASH_DUMPis enabled.[*] For verification reasons, this series only fixes coherent SMMUs.
For non-ARM_SMMU_OPT_KDUMP_ADOPT cases, keep a status quo since the commit
3f54c447df34f("iommu/arm-smmu-v3: Don't disable SMMU in kdump kernel"):
full reset followed by driver-initiated reattach, potentially rejecting any in-flight DMA.Note that this series is no longer treated as a bug fix, since it has grown fairly big and most of the kdump code now resides in a separate file. For folks interested in back-porting the change: a v6.12+ kernel (since commit
85196f54743d("iommu/arm-smmu-v3: Reorganize structarm_smmu_strtab_cfg")) would be still compatible with this series.
[...]
Quoted 12 lines
Nicolin Chen (9):
iommu/arm-smmu-v3: Do not enable EVTQ/PRIQ interrupts in kdump kernel iommu/arm-smmu-v3: Skip EVTQ/PRIQ setup in kdump kernel iommu/arm-smmu-v3: AddARM_SMMU_OPT_KDUMP_ADOPTfor kdump kernel iommu/arm-smmu-v3: Destroyvmid_mapida via devres iommu/arm-smmu-v3-kdump: Reserve crashed kernel's ASIDs and VMIDs iommu/arm-smmu-v3-kdump: Implementis_attach_deferred()iommu/arm-smmu-v3: RetainCR0_SMMUENduring kdump device reset iommu/arm-smmu-v3: Skip RMR bypass for kdump adoption iommu/arm-smmu-v3: DetectARM_SMMU_OPT_KDUMP_ADOPTinprobe()
Quoted 6 lines
drivers/iommu/arm/arm-smmu-v3/Makefile | 1 + drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h | 48 ++ .../iommu/arm/arm-smmu-v3/arm-smmu-v3-kdump.c | 579 ++++++++++++++++++ drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 246 ++++++-- 4 files changed, 806 insertions(+), 68 deletions(-) create mode 100644 drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-kdump.c
This series seems to align with the restore part of my SMMUv3 Live Update (Kexec Handover) support. I have a WIP series in dev on github:
https://github.com/pran005/linux/tree/wip-arm-smmu-lu
While going through the Stream Table adoption code in this series, I realized there is significant overlap between how kdump adopts a crashed kernel's SMMU structures and how we restore preserved SMMU state via Kexec HandOver (KHO) during a live update
For e.g., the KHO preservation hook in my series explicitly tracks and serializes the physical addresses of all active L1/L2 tables into the KHO Device Tree so the incoming kernel can kho_restore them.
However, looking at your approach, I think I can slightly rework my preservation logic and instead of bloating the KHO ABI with physical addresses, I could re-use your exact table-walking logic during probe to parse the live L1/L2 structures directly from registers, identify the valid tables, and kho/dma_restore them. There could me small differences though, for example instead of memremap stuff, we'd have to use the kho/dma_restore API (which can be done by passing some op like the data structure writers we have?) Similarly, maybe reserving ASID/VMID can be potentially re-used as well..
Since, I plan to introduce another file: arm-smmu-v3-liveupdate.c and given how much of this adoption and restoration logic is re-usable (parsing STRTAB_BASE, walking the L1 array, restoring L2s (not deferred for KHO), I wanted to start a discussion to see if it makes sense to factor this common code out into an arm-smmu-v3-kexec.c (or similar)?
I'm not trying to delay this series by any chance and I would be more than happy to rebase my Live Update series on top of this series and refactor to share this core logic between the 2 new files:arm-smmu-v3-kdump.c & arm-smmu-v3-liveupdate.c
I just wanted to start and early discussion since there's some overlap and align on a way forward.
Thanks,
Praan
Quoted 9 lines · Pranjal Shrivastava
However, looking at your approach, I think I can slightly rework my preservation logic and instead of bloating the KHO ABI with physical addresses, I could re-use your exact table-walking logic during probe to parse the live L1/L2 structures directly from registers, identify the valid tables, and kho/dma_restore them. There could me small differences though, for example instead of memremap stuff, we'd have to use the kho/dma_restore API (which can be done by passing some op like the data structure writers we have?) Similarly, maybe reserving ASID/VMID can be potentially re-used as well..
I think this will be true for all the iommu drivers as they pretty much all have this same kind of kdumpish adoption logic in one way or another.
Quoted 2 lines
for KHO), I wanted to start a discussion to see if it makes sense to factor this common code out into an
arm-smmu-v3-kexec.c(or similar)?
Yeah maybe so
It sounds great this helps the live update project as well!
Jason
Quoted 16 lines · Jason Gunthorpe
Quoted 9 lines · Pranjal Shrivastava
However, looking at your approach, I think I can slightly rework my preservation logic and instead of bloating the KHO ABI with physical addresses, I could re-use your exact table-walking logic during probe to parse the live L1/L2 structures directly from registers, identify the valid tables, and kho/dma_restore them. There could me small differences though, for example instead of memremap stuff, we'd have to use the kho/dma_restore API (which can be done by passing some op like the data structure writers we have?) Similarly, maybe reserving ASID/VMID can be potentially re-used as well..
I think this will be true for all the iommu drivers as they pretty much all have this same kind of kdumpish adoption logic in one way or another.
Quoted 6 lines
Quoted 2 lines
for KHO), I wanted to start a discussion to see if it makes sense to factor this common code out into an
arm-smmu-v3-kexec.c(or similar)?Yeah maybe so
It sounds great this helps the live update project as well!
I agree. I think the final layout can be:
# Kconfig
config ARM_SMMU_V3_KEXEC
- def_bool CRASH_DUMP
+ def_bool CRASH_DUMP || IOMMU_LIVEUPDATE
# Makefile
arm_smmu_v3-$(CONFIG_ARM_SMMU_V3_KEXEC) += arm-smmu-v3-kexec.o arm_smmu_v3-$(CONFIG_CRASH_DUMP) += arm-smmu-v3-kdump.o
+arm_smmu_v3-$(CONFIG_IOMMU_LIVEUPDATE) += arm-smmu-v3-liveupdate.o
Nicolin