The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Jiebin Sun <jiebin.sun@intel.com>
Cc: acme@kernel.org, mingo@redhat.com, peterz@infradead.org,
	adrian.hunter@intel.com, alexander.shishkin@linux.intel.com,
	irogers@google.com, james.clark@linaro.org, jolsa@kernel.org,
	mark.rutland@arm.com, dapeng1.mi@linux.intel.com,
	thomas.falcon@intel.com, tianyou.li@intel.com,
	wangyang.guo@intel.com, linux-perf-users@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 2/9] perf c2c: add function view browser skeleton
Date: Thu, 6 Aug 2026 23:13:13 -0700	[thread overview]
Message-ID: <anV3eQb6SzRnRksH@google.com> (raw)
In-Reply-To: <20260806074217.2846596-3-jiebin.sun@intel.com>

On Thu, Aug 06, 2026 at 03:42:10PM +0800, Jiebin Sun wrote:
> Add the skeleton of the c2c function view: a new TUI browser in
> tools/perf/ui/browsers/c2c-function.c reached by pressing TAB in the
> cacheline view. This commit wires up the entry point (a stub that will be
> filled in by later patches), declares perf_c2c__browse_function_view() in
> c2c.h, and adds the TAB key handler and help text to the cacheline browser.
> 
> Link c2c-function.o directly into perf rather than libperf-ui.a. The
> browser is part of the c2c command and later patches make it depend on
> state and callbacks provided by builtin-c2c.o. libperf-ui.a is also linked
> into python/perf.so under --whole-archive, without the builtin command
> objects, which would leave those command-private symbols unresolved.
> Build the browser only with CONFIG_SLANG, matching its TUI-only entry
> point.

I don't think it's a proper fix.  The c2c-function.o should belong to
libperf-ui.a.  Perhabs we can split libperf-tui.a and not link it to the
python module.  But still, it's better to move the common code into the
util directory.

Thanks,
Namhyung

  reply	other threads:[~2026-08-07  6:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06  7:42 [PATCH v7 0/9] perf c2c: add a function view Jiebin Sun
2026-08-06  7:42 ` [PATCH v7 1/9] perf c2c: extract shared data structures into c2c.h Jiebin Sun
2026-08-06  7:42 ` [PATCH v7 2/9] perf c2c: add function view browser skeleton Jiebin Sun
2026-08-07  6:13   ` Namhyung Kim [this message]
2026-08-06  7:42 ` [PATCH v7 3/9] perf c2c: add column rendering for function view Jiebin Sun
2026-08-06  7:42 ` [PATCH v7 4/9] perf c2c: add HPP list parsing for function view columns Jiebin Sun
2026-08-06  7:42 ` [PATCH v7 5/9] perf c2c: add function view stats merge and memory management Jiebin Sun
2026-08-06  7:42 ` [PATCH v7 6/9] perf c2c: add function view hierarchy entry creation Jiebin Sun
2026-08-06  7:42 ` [PATCH v7 7/9] perf c2c: build and finalize the function view hierarchy Jiebin Sun
2026-08-06  7:42 ` [PATCH v7 8/9] perf c2c: add function view browser UI and cacheline detail Jiebin Sun
2026-08-06  7:42 ` [PATCH v7 9/9] perf c2c: document function view in perf-c2c man page Jiebin Sun

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=anV3eQb6SzRnRksH@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=dapeng1.mi@linux.intel.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jiebin.sun@intel.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=thomas.falcon@intel.com \
    --cc=tianyou.li@intel.com \
    --cc=wangyang.guo@intel.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