From patchwork Fri Feb 2 22:04:45 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Namhyung Kim X-Patchwork-Id: 13543495 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 3687681739; Fri, 2 Feb 2024 22:05:01 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706911502; cv=none; b=cW7uf0Vz1602O6Jx63n2XYOp/8VgLOObwoBaNtZbAqmwB9yM/ALUl8OBEyAZg4qxWlpmYFvPxqL+o9zdsk5yY0jRxR4yTHcR/whR1tzgPH3xB31dGZpKMn6RWXL8ZLLmq+py0V7HjafSHpkXrUDxVJ2KhEZw1jAtHA9ZvR4rjJo= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706911502; c=relaxed/simple; bh=TtCatUXX54CpCPUlhHpPauZEMrRqJAFBr+hS8hCBFRQ=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=mhGv6AMYrfVkYnIikIHQSPhEWxWJJ9jgFlnJfGZgEk+o8ot50lYYPd+YH+C1gJKEzKVCPNFJUK3nRlMCNHbsjdGabNGFpGNTkhB1g2PXh9wbMS9b8cZjCk1ZpvL9e5xAerT/hCAyz6EEphPdE2AJNmNVxiRIKgCPX/I5oioZAxI= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=ZP62jWyA; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="ZP62jWyA" Received: by smtp.kernel.org (Postfix) with ESMTPSA id A38B7C433F1; Fri, 2 Feb 2024 22:05:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1706911501; bh=TtCatUXX54CpCPUlhHpPauZEMrRqJAFBr+hS8hCBFRQ=; h=From:To:Cc:Subject:Date:From; b=ZP62jWyAbrwzCAidfxlTdVO2bN6sXVxsdxU0i49taYN943OEwBV/+y7/ohbABc3h1 FG2271tLeqqNuTgfyMO9vevV4e2jlOzgay5+OjKsxy+yrycefmCQWvQPAjR7wdTF+o m2DQWFIi6mbq+ry0OVTi9uiMUiG7lvI6wA/0IrT6EUaEuk1bHiT3eTu0Qh0mP9MVAd 6jkbBVLUAxnH75ovmwX9B30szSeqP+DN8LGhclkHKU9tkFPrNLnkTJCXxTfHVqKDJh KkspmdFYGwFQF/D8aB3IqSB0IoCy+TxnpO0tzW5pQyO1lAHKS4eE5JOBpD8F2zUzlf QH1cWHlt7mlNA== From: Namhyung Kim To: Arnaldo Carvalho de Melo , Ian Rogers Cc: Jiri Olsa , Adrian Hunter , Peter Zijlstra , Ingo Molnar , LKML , linux-perf-users@vger.kernel.org, Linus Torvalds , Stephane Eranian , Masami Hiramatsu , linux-toolchains@vger.kernel.org, linux-trace-devel@vger.kernel.org, Ben Woodard , Joe Mario , Kees Cook , David Blaikie , Xu Liu , Kan Liang , Ravi Bangoria , Mark Wielaard , Jason Merrill , "Jose E . Marchesi" , William Huang Subject: [PATCHSET 00/14] perf tools: Remaining bits of data type profiling (v5) Date: Fri, 2 Feb 2024 14:04:45 -0800 Message-ID: <20240202220459.527138-1-namhyung@kernel.org> X-Mailer: git-send-email 2.43.0.594.gd9cf4e227d-goog Precedence: bulk X-Mailing-List: linux-trace-devel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Hello, This is the last part of the data type profiling series. So far we added the basic pointer variable support, and direct access to global/local variables. Now it's time to add instruction tracking. :) For the history and background, you can refer to the previous version [1] and the LWN article [2]. Basically it needs to track variable (and its type) assignment to get a type of memory access at the sampled instruction. Compilers don't generate DWARF information for every memory accesses so it cannot find all the necessary information from DWARF. Therefore, it follows the path to the sample in the function, and update type information at each location when the instruction moves it. For the DWARF search, it has a list of scope entries (subroutines or blocks) that covers the sample already. So it can use the scopes to find the shortest path to the sample instruction. Let's say we have this. It got 5 scopes but couldn't find a matching variable for the sample. +---------------- scope[0] subprogram | | +-------------- scope[1] lexical_block | | | | +------------ scope[2] inlined_subroutine | | | | | | +---------- scope[3] inlined_subroutine | | | | | | | | +-------- scope[4] lexical_block | | | | | | | | | | *** target instruction ... Then it starts with the closest scope (at index 4), and find the shortest path from the start of the scope to the target instruction. Along the way, it updates type information in the scope and see if the location at the target instruction has the type. If so, it can return with the type. Otherwise, it goes to the scope[3] and find the shortest path from the start of scope[3] to the start of scope[4]. And then it can combine the existing shortest path from the scope[4] to the target with the new path. Now it can start from the scope[3] with new variables and types. It can repeat this algorithm for the outer scopes. I did it this way because mostly it was able to find a type in the closest scope. So it can avoid unnecessary work for outer scopes. And it added a basic per-cpu variable support for this CPU on x86_64 which uses %gs segment register. Also it can detect the stack-canary pattern which is added by compiler to detect stack overflow. The code is available at 'perf/data-profile-v5' branch in the tree below. I've dropped the debug patch at the end in this series but you can find it in the git branch. git://git.kernel.org/pub/scm/linux/kernel/git/namhyung/linux-perf.git Thanks, Namhyung Cc: Ben Woodard Cc: Joe Mario CC: Kees Cook Cc: David Blaikie Cc: Xu Liu Cc: Kan Liang Cc: Ravi Bangoria Cc: Mark Wielaard Cc: Jason Merrill Cc: Jose E. Marchesi Cc: William Huang [1] https://lore.kernel.org/linux-perf-users/20231110000012.3538610-1-namhyung@kernel.org/ [2] https://lwn.net/Articles/955709/ Namhyung Kim (14): perf dwarf-aux: Add die_collect_vars() perf dwarf-aux: Handle type transfer for memory access perf annotate-data: Introduce struct data_loc_info perf map: Add map__objdump_2rip() perf annotate: Add annotate_get_basic_blocks() perf annotate-data: Maintain variable type info perf annotate-data: Add update_insn_state() perf annotate-data: Handle global variable access perf annotate-data: Handle call instructions perf annotate-data: Implement instruction tracking perf annotate: Parse x86 segment register location perf annotate-data: Handle this-cpu variables in kernel perf annotate-data: Track instructions with a this-cpu variable perf annotate-data: Add stack canary type tools/perf/util/annotate-data.c | 710 ++++++++++++++++++++++++++++++-- tools/perf/util/annotate-data.h | 87 +++- tools/perf/util/annotate.c | 366 ++++++++++++++-- tools/perf/util/annotate.h | 38 ++ tools/perf/util/dwarf-aux.c | 232 +++++++++-- tools/perf/util/dwarf-aux.h | 23 ++ tools/perf/util/map.c | 20 + tools/perf/util/map.h | 3 + 8 files changed, 1373 insertions(+), 106 deletions(-)