Re: [PATCH 3/4] Revert "x86: disable IOMMUs on kernel crash"
From: Eric W. Biederman
Date: Sun Apr 04 2010 - 05:45:05 EST
Joerg Roedel <joro@xxxxxxxxxx> writes:
> On Sun, Apr 04, 2010 at 09:24:30AM +0200, Bernhard Walle wrote:
>> Am 03.04.10 19:49, schrieb Eric W. Biederman:
>> > Not a problem. We require a lot of things of the kdump kernel,
>> > and it is immediately apparent in a basic sanity test.
>> Also, in most cases (for example: distribution kernels), the kdump
>> kernel nowadays is identical to the running kernel. So, if the running
>> kernel has IOMMU support, the kdump kernel also has.
> Yes, I know. But is that a requirement for kexec?
For normal kexec no. That path is expected to do a clean hardware
For kexec on panic aka kdump the requirement is that your your crash
kernel be able to initialize your hardware from any state it can be
Currently we have no kernels that properly recover and amd-iommu and
it is not a requirement that we cater to broken kernels.
> If not we still
> potentially have this problem. It is a smaller problem than
> data-corruption caused by in-flight dma because most
> people^Wdistributions indeed use the same kernel for normal boot and
> kexec, thats true.
There are exceptions made for practical reality. The fact that
typically the kdump kernel is the same as the running kernel mean that
we don't even need to consider one of those exceptions.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/