In place kexec
Eric W. Biederman
ebiederm at xmission.com
Thu Jul 29 14:06:50 EDT 2010
"H. Peter Anvin" <hpa at zytor.com> writes:
> On 07/29/2010 08:06 AM, Neil Horman wrote:
>>> Sorry, can we keep the discussions of kexec-on-crash and kexec-in-place
>>> clearly separated, please? The qla driver issue is supposed to be
>>> kexec-in-place, and it sounds like you're talking about kexec-on-crash.
>> No, I'm just indicating a difference between the two paths, and I'm doing so
>> because we used to have simmilar dma problems in the crash path, which we
>> resolved by not turning of the iommu during shutdown, which is different from
>> the in-place path. Just trying to give you some thoughts about where to look
> Fair enough... just wanted to flag this as a problem, because it has
> already been the source of a lot of confusion.
Thinking about this I am a bit surprised that you would find
DMA left on from a disk driver. Historically disks have been
pretty good about shutting off in this scenario.
Added to that typically we unmount all filesystems.
Calling rmmod on the driver before the final kexec --exec
could be interesting, and drivers much more reliably implement
.remove than .shutdown.
Network drivers are more likely to be a problem, but we should be
downing all of the network interfaces before something happens.
All of which is to say kexec-in-place has generally been a lot
less hassle, because it is so similar to the normal case.
More information about the kexec