[PATCH v10 0/10] iommu/vt-d: Fix intel vt-d faults in kdump kernel
dyoung at redhat.com
Fri Apr 24 01:25:28 PDT 2015
> I support this patchset.
> We should not fear oldmem since reserved crashkernel region is similar.
> No one can guarantee that any crazy code won't step into crashkernel
> region just because 1st kernel says it's reversed for kdump kernel. Here
> the root table and context tables are also not built to allow legal code
> to danamge. Both of them has the risk to be corrupted, for trying our
> best to get a dumped vmcore the risk is worth being taken.
old mem is mapped in 1st kernel so compare with the reserved crashkernel
they are more likely to be corrupted. they are totally different.
> And the resetting pci way has been NACKed by David Woodhouse, the
> maintainer of intel iommu. Because the place calling the resetting pci
> code is ugly before kdump kernel or in kdump kernel. And as he said a
> certain device made mistakes why we blame on all devices. We should fix
> that device who made mistakes.
Resetting pci bus is not ugly than fixing a problem with risk and to fix
the problem it introduced in the future.
I know it is late to speak out, but sorry I still object and have to NACK this
oldmem approach from my point.
More information about the kexec