From: "tenglong.tl" <dyroneteng@gmail.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, --cc=avarab@gmail.com, git@jeffhostetler.com,
tenglong.tl@alibaba-inc.com, Teng Long <dyroneteng@gmail.com>
Subject: [PATCH 1/2] api-trace2.txt: print config key-value pair
Date: Thu, 21 Jul 2022 21:27:47 +0800 [thread overview]
Message-ID: <20220721132748.37848-2-tenglong.tl@alibaba-inc.com> (raw)
In-Reply-To: <20220721132748.37848-1-tenglong.tl@alibaba-inc.com>
From: Teng Long <dyroneteng@gmail.com>
It's supported to print "interesting" config key-value paire
to tr2 log by setting "GIT_TRACE2_CONFIG_PARAMS" environment
variable and the "trace2.configparam" config, let's add the
related docs in Documentaion/technical/api-trace2.txt.
Signed-off-by: Teng Long <dyroneteng@gmail.com>
---
Documentation/technical/api-trace2.txt | 31 ++++++++++++++++++++++++++
1 file changed, 31 insertions(+)
diff --git a/Documentation/technical/api-trace2.txt b/Documentation/technical/api-trace2.txt
index 77a150b30e..dcd0429037 100644
--- a/Documentation/technical/api-trace2.txt
+++ b/Documentation/technical/api-trace2.txt
@@ -1207,6 +1207,37 @@ at offset 508.
This example also shows that thread names are assigned in a racy manner
as each thread starts and allocates TLS storage.
+Print Configs::
+
+ Dump "interesting" config values to trace2 log.
++
+The environment variable `GIT_TRACE2_CONFIG_PARAMS` and configuration
+`trace2.configparams` can be used to output config values which you care
+about(see linkgit:git-config[1). For example:
++
+----------------
+$ git config color.ui auto
+----------------
++
+Then, mark the config `color.ui` as "interesting" config with
+`GIT_TRACE2_CONFIG_PARAMS`:
++
+----------------
+$ export GIT_TRACE2_PERF_BRIEF=1
+$ export GIT_TRACE2_PERF=~/log.perf
+$ export GIT_TRACE2_CONFIG_PARAMS=color.ui
+$ git version
+...
+$ cat ~/log.perf
+d0 | main | version | | | | | ...
+d0 | main | start | | 0.001642 | | | /usr/local/bin/git version
+d0 | main | cmd_name | | | | | version (version)
+d0 | main | def_param | | | | | color.ui:auto
+d0 | main | data | r0 | 0.002100 | 0.002100 | fsync | fsync/writeout-only:0
+d0 | main | data | r0 | 0.002126 | 0.002126 | fsync | fsync/hardware-flush:0
+d0 | main | exit | | 0.002142 | | | code:0
+d0 | main | atexit | | 0.002161 | | | code:0
+----------------
== Future Work
=== Relationship to the Existing Trace Api (api-trace.txt)
--
2.37.1.1.g8cbb44ffc4.dirty
next prev parent reply other threads:[~2022-07-21 13:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 13:27 [PATCH 0/2] tr2: shows the scope unconditionally with config tenglong.tl
2022-07-21 13:27 ` tenglong.tl [this message]
2022-07-21 13:27 ` [PATCH 2/2] tr2: shows scope unconditionally in addition to key-value pair tenglong.tl
2022-07-21 16:57 ` Junio C Hamano
2022-07-22 6:12 ` tenglong.tl
2022-07-22 8:19 ` [PATCH v1 0/2] tr2: shows the scope unconditionally with config tenglong.tl
2022-07-22 8:19 ` [PATCH v1 1/2] api-trace2.txt: print config key-value pair tenglong.tl
2022-07-22 10:59 ` Ævar Arnfjörð Bjarmason
2022-07-25 19:07 ` Junio C Hamano
2022-08-01 12:25 ` tenglong.tl
2022-08-05 22:21 ` Junio C Hamano
2022-08-08 6:16 ` Teng Long
2022-07-22 21:05 ` Junio C Hamano
2022-07-23 6:06 ` tenglong.tl
2022-07-23 17:47 ` Junio C Hamano
2022-07-25 9:18 ` tenglong.tl
2022-07-22 8:19 ` [PATCH v1 2/2] tr2: shows scope unconditionally in addition to " tenglong.tl
2022-08-12 2:56 ` [PATCH v2 0/2] tr2: shows the scope unconditionally with config Teng Long
2022-08-12 2:56 ` [PATCH v2 1/2] api-trace2.txt: print config key-value pair Teng Long
2022-08-12 2:56 ` [PATCH v2 2/2] tr2: shows scope unconditionally in addition to " Teng Long
2022-08-12 21:16 ` Junio C Hamano
2022-08-19 21:18 ` [PATCH v2 0/2] tr2: shows the scope unconditionally with config Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220721132748.37848-2-tenglong.tl@alibaba-inc.com \
--to=dyroneteng@gmail.com \
--cc=--cc=avarab@gmail.com \
--cc=git@jeffhostetler.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=tenglong.tl@alibaba-inc.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).