[lkml]   [2019]   [Mar]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[PATCH v2 0/2] iommu/arm-smmu-v3: make sure the kdump kernel can work well when smmu is enabled
v1 --> v2:
1. Drop part2. Now, we only use the SMMUv3 hardware feature STE.config=0b000
(Report abort to device, no event recorded) to suppress the event messages
caused by the unexpected devices.
2. rewrite the patch description.

This patch series include two parts:
1. Patch1-2 use dummy STE tables with "ste abort" hardware feature to abort unexpected
devices accessing. For more details, see the description in patch 2.
2. If the "ste abort" feature is not support, force the unexpected devices in the
secondary kernel to use the memory maps which it used in the first kernel. For more
details, see patch 5.

Zhen Lei (2):
iommu/arm-smmu-v3: make sure the stale caching of L1STD are invalid
iommu/arm-smmu-v3: to make smmu can be enabled in the kdump kernel

drivers/iommu/arm-smmu-v3.c | 88 +++++++++++++++++++++++++++++++++------------
1 file changed, 65 insertions(+), 23 deletions(-)


 \ /
  Last update: 2019-03-18 14:14    [W:0.141 / U:1.768 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site