LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: x86-ml <x86@kernel.org>, Peter Zijlstra <peterz@infradead.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Andy Lutomirski <luto@amacapital.net>,
	lkml <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [GIT PULL] x86/alternatives padding
Date: Wed, 4 Mar 2015 22:02:43 +0100	[thread overview]
Message-ID: <20150304210243.GH3516@pd.tnic> (raw)
In-Reply-To: <20150304202227.GA6826@gmail.com>

On Wed, Mar 04, 2015 at 09:22:27PM +0100, Ingo Molnar wrote:
> So you could have a look at the detailed section dump itself via:
> 
>    objdump -h vmlinux
> 
> there .text will be the raw text and .alt* will be listed separately. 
> The 'size' tool will add up executable sections IIRC, mixing these 
> sections.

Right.

> .alt* is freed after init, so it's not really a kernel image size 
> increase, right?

Exactly:

void free_initmem(void)
{
        free_init_pages("unused kernel",
                        (unsigned long)(&__init_begin),
                        (unsigned long)(&__init_end));
}

which are:

 69708: ffffffff81ee9000     0 NOTYPE  GLOBAL DEFAULT   16 __init_begin
 72679: ffffffff81ff9000     0 NOTYPE  GLOBAL DEFAULT   25 __init_end

and there's a bunch of stuff between ffffffff81ee9000 and ffffffff81ff9000:

  [Nr] Name              Type             Address           Offset
       Size              EntSize          Flags  Link  Info  Align
  [17] .init.text        PROGBITS         ffffffff81efe000  012fe000
       0000000000066c98  0000000000000000  AX       0     0     16
  [18] .init.data        PROGBITS         ffffffff81f65000  01365000
       0000000000086d18  0000000000000000  WA       0     0     4096
  [19] .x86_cpu_dev.init PROGBITS         ffffffff81febd18  013ebd18
       0000000000000018  0000000000000000   A       0     0     8
  [20] .altinstructions  PROGBITS         ffffffff81febd30  013ebd30
       0000000000007e4b  0000000000000000   A       0     0     1
  [21] .altinstr_replace PROGBITS         ffffffff81ff3b7b  013f3b7b
       0000000000002044  0000000000000000  AX       0     0     1
  [22] .iommu_table      PROGBITS         ffffffff81ff5bc0  013f5bc0
       00000000000000c8  0000000000000000   A       0     0     8
  [23] .apicdrivers      PROGBITS         ffffffff81ff5c88  013f5c88
       0000000000000010  0000000000000000  WA       0     0     8
  [24] .exit.text        PROGBITS         ffffffff81ff5c98  013f5c98
       0000000000002412  0000000000000000  AX       0     0     1

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--

      reply	other threads:[~2015-03-04 21:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03 17:06 Borislav Petkov
2015-03-04  7:32 ` Ingo Molnar
2015-03-04 11:22   ` Borislav Petkov
2015-03-04 11:41     ` Borislav Petkov
2015-03-04 20:22       ` Ingo Molnar
2015-03-04 21:02         ` Borislav Petkov [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=20150304210243.GH3516@pd.tnic \
    --to=bp@alien8.de \
    --cc=acme@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    --subject='Re: [GIT PULL] x86/alternatives padding' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).