All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiebin Sun <jiebin.sun@intel.com>
To: namhyung@kernel.org
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, Jiebin Sun <jiebin.sun@intel.com>
Subject: Re: [PATCH v7 2/9] perf c2c: add function view browser skeleton
Date: Mon, 10 Aug 2026 13:34:00 +0800	[thread overview]
Message-ID: <20260810053401.590185-1-jiebin.sun@intel.com> (raw)
In-Reply-To: <anV3eQb6SzRnRksH@google.com>

Hi Namhyung,

> 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. I reworked this in v8 to keep c2c-function.o in libperf-ui.a and
removed the v7 tools/perf/Build change.

builtin-c2c.c now passes the cacheline histograms, the --coalesce field
list, symbol_full, and the cacheline detail callback through
struct c2c_function_view_args. The browser no longer references the
command-private c2c instance or perf_c2c__browse_cacheline().

The shared c2c types and formatter callbacks are now in util/c2c.h and
util/c2c.c. struct perf_c2c and the command state remain private to
builtin-c2c.c.

Thanks,
Jiebin

  reply	other threads:[~2026-08-10  5:27 UTC|newest]

Thread overview: 14+ 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
2026-08-10  5:34     ` Jiebin Sun [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:47   ` sashiko-bot
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:54   ` sashiko-bot
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=20260810053401.590185-1-jiebin.sun@intel.com \
    --to=jiebin.sun@intel.com \
    --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=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=namhyung@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.