Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Geoff Levand <geoff@infradead.org>
Cc: panand@redhat.com, kexec@lists.infradead.org,
	Simon Horman <horms@verge.net.au>,
	Petitboot@lists.ozlabs.org, Dave Young <dyoung@redhat.com>,
	Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [PATCH] kexec: Add --lite option
Date: Wed, 4 Nov 2015 23:56:51 -0600	[thread overview]
Message-ID: <1446703011.12676.83.camel@freescale.com> (raw)
In-Reply-To: <1445540891.30908.144.camel@infradead.org>

On Thu, 2015-10-22 at 12:08 -0700, Geoff Levand wrote:
> Hi Vivek,
> 
> On Thu, 2015-10-22 at 08:50 -0400, Vivek Goyal wrote:
> > On Thu, Oct 22, 2015 at 11:17:18AM +0800, Dave Young wrote:
> > > On 10/21/15 at 04:12pm, Geoff Levand wrote:
> > > > Add a new option --lite 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.
> > > 
> > > I think Vivek was rejecting this --lite since kdump need the purgatory
> > > integrity checks. Ccing him.
> > 
> > Right. Why are we trying to bypass sha256 hash verification of loaded
> > segments at run time, that needs to be justified. 
> 
> Please see my reply to Dave.
> 
> > Atleast on x86, this integrity verification was fast and we did not
> > notice any siginificant delays in purgatory. And in that case extra knob
> > like this is hard to justify.
> 
> I notice the difference on the my arm64 system, so I guess we
> are even on that.

For me it was beyond "notice the difference" -- I thought it was completely 
broken, and was preparing to debug, until it started spitting out output over 
a minute later.

Compiling the sha256 code with -O2 instead of -O0 cut it down to around 10 
seconds (still unpleasant, but not quite as crazy... still unacceptable for 
non-kdump, though).  There was a patch posted a couple years ago to do that --
does anyone know what happened to it?

http://kexec.infradead.narkive.com/JSemzXoT/patch-purgatory-compile-sha256-c-only-on-ia64-with-o0

-Scott



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

  reply	other threads:[~2015-11-05  5:57 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 [this message]
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
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=1446703011.12676.83.camel@freescale.com \
    --to=scottwood@freescale.com \
    --cc=Petitboot@lists.ozlabs.org \
    --cc=dyoung@redhat.com \
    --cc=geoff@infradead.org \
    --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