Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Geoff Levand <geoff@infradead.org>
To: Dave Young <dyoung@redhat.com>
Cc: panand@redhat.com, Simon Horman <horms@verge.net.au>,
	kexec@lists.infradead.org, Petitboot@lists.ozlabs.org,
	vgoyal@redhat.com
Subject: Re: [PATCH] kexec: Add --lite option
Date: Fri, 23 Oct 2015 11:49:43 -0700	[thread overview]
Message-ID: <1445626183.30908.198.camel@infradead.org> (raw)
In-Reply-To: <20151023094620.GG11227@dhcp-129-115.nay.redhat.com>

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


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2015-10-23 18:49 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21 23:12 [PATCH] kexec: Add --lite option Geoff Levand
2015-10-22  0:02 ` Jeremy Kerr
2015-10-22  0:37   ` Geoff Levand
2015-11-05  6:20     ` Scott Wood
2015-10-22  3:17 ` Dave Young
2015-10-22 12:50   ` Vivek Goyal
2015-10-22 19:08     ` Geoff Levand
2015-11-05  5:56       ` Scott Wood
2015-12-07 11:45         ` Pratyush Anand
2015-12-07 11:48           ` Pratyush Anand
2015-12-07 13:16             ` James Morse
2015-12-07 14:07               ` Pratyush Anand
2015-12-08  1:03                 ` Scott Wood
2015-12-08 16:00                 ` James Morse
2015-12-09  9:28                   ` Pratyush Anand
2016-01-11 12:46                     ` Pratyush Anand
2016-01-12  1:06                       ` Simon Horman
2015-10-22 18:57   ` Geoff Levand
2015-10-22 19:04     ` Vivek Goyal
2015-10-23  9:46     ` Dave Young
2015-10-23 18:49       ` Geoff Levand [this message]
2015-10-23 19:02     ` Eric W. Biederman
2018-04-11 18:30 ` [PATCH v2] kexec: Add --no-checks option Geoff Levand
2018-04-19  8:38   ` Simon Horman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1445626183.30908.198.camel@infradead.org \
    --to=geoff@infradead.org \
    --cc=Petitboot@lists.ozlabs.org \
    --cc=dyoung@redhat.com \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=panand@redhat.com \
    --cc=vgoyal@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox