Hi Dave, On Fri, 2015-10-23 at 17:46 +0800, Dave Young wrote: > On 10/22/15 at 11:57am, Geoff Levand wrote: > > As stated, this is not intended for use by kdump. > > > > This is an optional feature. It does not remove the integrity > > checks, but provides the user a way to bypass them if they so > > desire. > > Problem is why they so desire to skip purgatory? what is the background? This doesn't remove or skip purgatory. Purgatory is still used. What it does do is skip the digest calculations that are done when an image is loaded (kexec --load), and it skips the digest calculations and comparison when the new image is run (kexec --exec). The digest check is great for kdump, where the crash kernel is loaded, and some time later a possibly unstable system tries to do a kexec and we want to assure the integrity of the new image. Kexec based bootloaders are very different. They are running in a stable state. They load a new image and immediately transfer control to that new image. Because the system is in a stable state, and very little is done between the time the image is loaded and the time it is entered, there is little reason to do an integrity check, and by avoiding it we can speed up the boot process. Faster boot (and re-boot) time is important to users, vendors, highly available systems, they all want it. -Geoff
