linux-kernel - why is CONFIG_FRAME_POINTER=y so expensive?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <1471846671.4139.50.camel@gmail.com>
Date:   Mon, 22 Aug 2016 08:17:51 +0200
From:   Mike Galbraith <umgwanakikbuti@...il.com>
To:     LKML <linux-kernel@...r.kernel.org>
Cc:     Ingo Molnar <mingo@...e.hu>
Subject: why is CONFIG_FRAME_POINTER=y so expensive?

Greetings,

tbench 8 throughput on my i4790 box:
                              1        2        3      avg
master                  3769.95  3759.28  3762.83  3764.02  1.000
master-framepointer     3476.73  3453.52  3460.62  3463.62   .920

Does anyone know why the performance impact is this large?

The only thing I found googling was a reference to 3 arg lea using rbp
or r13 being slow, which wasn't particularly helpful.  Nor was staring
at asm deltas with non-expert eyeballs.

	-Mike