Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   John Garry <john.garry@huawei.com>
To:     <will@kernel.org>, <catalin.marinas@arm.com>,
        <linux-arm-kernel@lists.infradead.org>, <arnd@arndb.de>,
        <olof@lixom.net>, <soc@kernel.org>
CC:     <jpoimboe@kernel.org>, <linux-kernel@vger.kernel.org>,
        John Garry <john.garry@huawei.com>
Subject: [PATCH 0/2] arm64 defconfig: Get faddr2line working
Date:   Mon, 25 Jul 2022 00:43:22 +0800
Message-ID: <1658681004-132191-1-git-send-email-john.garry@huawei.com>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk

scripts/faddr2line has not worked by default for arm64 since 5.17

Firstly, since commit f9b3cd245784 ("Kconfig.debug: make DEBUG_INFO
selectable from a choice"), CONFIG_DEBUG_INFO was not getting enabled by
default (and this is required for faddr2line to work).

Secondly, commit dcea997beed6 ("faddr2line: Fix overlapping text section
failures, the sequel") caused a breakage for arm64, as reported at the
following:
https://lore.kernel.org/lkml/3bd9817d-1959-c081-e5d0-8b0e70b3f41e@huawei.com/

Josh has sent fixes/improvements for faddr2line at the following:
https://lore.kernel.org/lkml/cover.1658426357.git.jpoimboe@kernel.org/

In this series I enable CONFIG_DEBUG_INFO by enabling
CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT, which seems the sensible
option.

As for merging this, I am not sure who would pick it up - any takers
welcome.

Note: this is based on next-20220722 and it may be wiser to sync the
defconfig manually (instead of using 1/2). Indeed I am not sure what is
the policy is of sync'ing this anyway.

Thanks! 

John Garry (2):
  arm64: defconfig: Sync with savedefconfig
  arm64: defconfig: Enable DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT

 arch/arm64/configs/defconfig | 85 ++++++++++++++++--------------------
 1 file changed, 37 insertions(+), 48 deletions(-)

-- 
2.35.3