All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Geoff Levand <geoff@infradead.org>
Cc: James Morse <james.morse@arm.com>,
	Kostiantyn Iarmak <kiarmak@cisco.com>,
	kexec@lists.infradead.org, Petitboot@lists.ozlabs.org
Subject: Re: [PATCH v2] kexec: Add --no-checks option
Date: Thu, 19 Apr 2018 10:38:45 +0200	[thread overview]
Message-ID: <20180419083845.qmdol6a5xm57vry7@verge.net.au> (raw)
In-Reply-To: <fc68e396-1eab-7cc3-fcbd-01b03e5967cb@infradead.org>

On Wed, Apr 11, 2018 at 11:30:48AM -0700, Geoff Levand wrote:
> Add a new option --no-checks to kexec that allows for a fast
> reboot by avoiding the purgatory integrity checks.  This option is
> intended for use by kexec based bootloaders that load a new
> image and then immediately transfer control to it.
> 
> Signed-off-by: Geoff Levand <geoff@infradead.org>
> ---
> Hi Simon,
> 
> On 10/21/2015 04:12 PM, Geoff Levand wrote:
> > Hi Simon,
> > 
> > It was reported that on some systems where purgatory is running
> > without caches enabled the sha256 calculations would take several
> > minutes.  For bootloaders that just load a new image and
> > immediately jump into it the loss of the integrity check is worth
> > the increase in boot speed.  Please consider.
> 
> There seems to be continued interest in faster kexec re-boot times
> on arm64 systems so I rebased my old patch and renamed the
> option from '--lite' to '--no-checks'.  Please consider.

Thanks, applied.

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

      reply	other threads:[~2018-04-19  8:39 UTC|newest]

Thread overview: 32+ 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 11:48             ` Pratyush Anand
2015-12-07 13:16             ` James Morse
2015-12-07 13:16               ` James Morse
2015-12-07 14:07               ` Pratyush Anand
2015-12-07 14:07                 ` Pratyush Anand
2015-12-08  1:03                 ` Scott Wood
2015-12-08  1:03                   ` Scott Wood
2015-12-08 16:00                 ` James Morse
2015-12-08 16:00                   ` James Morse
2015-12-09  9:28                   ` Pratyush Anand
2015-12-09  9:28                     ` Pratyush Anand
2016-01-11 12:46                     ` Pratyush Anand
2016-01-11 12:46                       ` Pratyush Anand
2016-01-12  1:06                       ` Simon Horman
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
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 [this message]

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=20180419083845.qmdol6a5xm57vry7@verge.net.au \
    --to=horms@verge.net.au \
    --cc=Petitboot@lists.ozlabs.org \
    --cc=geoff@infradead.org \
    --cc=james.morse@arm.com \
    --cc=kexec@lists.infradead.org \
    --cc=kiarmak@cisco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.