public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Tony Lindgren <tony@atomide.com>
Cc: Roger Shimizu <rogershimizu@gmail.com>,
	Corentin Chary <corentincj@iksaif.net>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Michal Marek <mmarek@suse.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] scripts: make extract-vmlinux support armel/armhf
Date: Sat, 2 Sep 2017 00:16:54 +0100	[thread overview]
Message-ID: <20170901231654.GY20805@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20170831174318.GM6008@atomide.com>

On Thu, Aug 31, 2017 at 10:43:19AM -0700, Tony Lindgren wrote:
> * Russell King - ARM Linux <linux@armlinux.org.uk> [170831 09:21]:
> > On Fri, Sep 01, 2017 at 01:05:16AM +0900, Roger Shimizu wrote:
> > > On Fri, Sep 1, 2017 at 12:49 AM, Russell King - ARM Linux
> > > <linux@armlinux.org.uk> wrote:
> > > > What's the use case - what are you using the output of this script with?
> > > 
> > > I already provided a use case, to trace a Debian kernel issue caused
> > > by kernel size.
> > > - https://bugs.debian.org/870185#50
> > 
> > Sorry, I haven't time to look - it needs me to use firefox on a
> > different machine.  Maybe you could help by providing some details
> > by email, otherwise I've got extra work to do at some point in the
> > future (probably days away) if I remember (your mail will get buried).
> > Much of my time is in front of a _textual_ _only_ interface, and elinks
> > does not work with several modern SSL-only sites.
> > 
> > > I also see other people complaining this issue:
> > >  - https://bugs.launchpad.net/linaro-ubuntu/+bug/1050453
> > >  - https://bugs.linaro.org/show_bug.cgi?id=461
> > > 
> > > By a random web search, I find another blog post on how to dissamble the kernel.
> > >  - https://blog.packagecloud.io/eng/2016/03/08/how-to-extract-and-disassmble-a-linux-kernel-image-vmlinuz/
> > 
> > Yea, all SSL sites, I'm not going to try elinks with them, I don't
> > have the time to mess around.
> 
> I think the use case is to get the booted kernel size from zImage
> to avoid overwriting dts or initramfs. Don't we already have that
> at the end of zImage somewhere for kexec?

We do, but finding where that is is difficult if a DTB has been appended
as it's right at the end of the compressed data.  kexec doesn't use it,
it just assumes there's a 5x expansion of the kernel compressed image.

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 8.8Mbps down 630kbps up
According to speedtest.net: 8.21Mbps down 510kbps up

  reply	other threads:[~2017-09-01 23:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-31 15:36 [PATCH] scripts: make extract-vmlinux support armel/armhf Roger Shimizu
2017-08-31 15:49 ` Russell King - ARM Linux
2017-08-31 16:05   ` Roger Shimizu
2017-08-31 16:19     ` Russell King - ARM Linux
2017-08-31 17:43       ` Tony Lindgren
2017-09-01 23:16         ` Russell King - ARM Linux [this message]
2017-09-09  7:33           ` Roger Shimizu
2017-09-09  9:06             ` Russell King - ARM Linux
2017-09-09 14:27     ` Russell King - ARM Linux

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=20170901231654.GY20805@n2100.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=corentincj@iksaif.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=mmarek@suse.com \
    --cc=rogershimizu@gmail.com \
    --cc=tony@atomide.com \
    --cc=yamada.masahiro@socionext.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