From: Andi Kleen <andi@firstfloor.org>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: Andi Kleen <andi@firstfloor.org>,
mingo@elte.hu, acme@redhat.com, linux-kernel@vger.kernel.org,
Andi Kleen <ak@linux.intel.com>,
mlpesant@us.ibm.com
Subject: Re: [PATCH 15/15] perf, tools: Add perf stat --transaction v3
Date: Thu, 27 Jun 2013 05:49:11 +0200 [thread overview]
Message-ID: <20130627034911.GO6123@two.firstfloor.org> (raw)
In-Reply-To: <20130627031854.GA9793@concordia>
> OK. I'm still confused by that one sorry. In the patch you do:
>
> + else if (perf_evsel__cmp(counter, nth_evsel(T_CYCLES_IN_TX_CP)))
> + update_stats(&runtime_cycles_in_txcp_stats[0], count[0]);
>
> But then I don't see where you use runtime_cycles_in_txcp_stats ?
You're right that variable is not needed. I'll remove it.
It only needs the in_tx stat.
intx-cp is still output, but directly by abs_printout,
without going through a variable.
>
> > > But I don't think we have anything equivalent.
> >
> > But you have cycles-t and tx-start?
>
> We have:
> - cycles
> - cycles in transactional state
> - cycles spent in successful transactions
>
> So your cycles-t is "cycles in transactional state".
>
> We would calculate cycles wasted in aborts with:
>
> "cycles in transactional" - "cycles in successful transactions"
>
> Which I think is what you're describing above with cycles-ct.
Yes, that should be equivalent.
That should be easy to check for and handle: check for that
event and switch the formula around.
I'll leave that to you as I don't have any way to test it.
> Does "tx-start" just count the number of transactions begun? Does it
> count nested transactions?
Just begun without nesting (TSX flattens all transactions)
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
prev parent reply other threads:[~2013-06-27 3:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-20 19:19 perf PMU support for Haswell v8 Andi Kleen
2013-04-20 19:19 ` [PATCH 01/15] perf, x86: Suppress duplicated abort LBR records Andi Kleen
2013-04-20 19:19 ` [PATCH 02/15] perf, x86: Disable software LBR filter for Sandy Bridge/Haswell Andi Kleen
2013-04-20 19:19 ` [PATCH 03/15] perf, x86: Support full width counting v3 Andi Kleen
2013-04-20 19:19 ` [PATCH 04/15] perf, tools: Support sorting by in_tx, abort branch flags v3 Andi Kleen
2013-04-20 19:19 ` [PATCH 05/15] perf, tools: Add abort_tx,no_tx,in_tx branch filter options to perf record -j v3 Andi Kleen
2013-04-20 19:19 ` [PATCH 06/15] perf, x86: Support the TSX intx/intx_cp qualifiers v4 Andi Kleen
2013-04-20 19:19 ` [PATCH 07/15] perf, x86: Avoid checkpointed counters causing excessive TSX aborts v4 Andi Kleen
2013-04-20 19:19 ` [PATCH 08/15] perf, kvm: Support the intx/intx_cp modifiers in KVM arch perfmon emulation v5 Andi Kleen
2013-04-23 8:48 ` Gleb Natapov
2013-04-20 19:19 ` [PATCH 09/15] perf, x86: Support PERF_SAMPLE_ADDR for all PEBS events v3 Andi Kleen
2013-04-20 19:19 ` [PATCH 10/15] perf, core: Add generic transaction flags v3 Andi Kleen
2013-04-20 19:19 ` [PATCH 11/15] perf, x86: Add Haswell specific transaction flag reporting Andi Kleen
2013-04-20 19:19 ` [PATCH 12/15] perf, tools: Add support for record transaction flags v3 Andi Kleen
2013-04-20 19:19 ` [PATCH 13/15] tools, perf: Add a precise event qualifier v2 Andi Kleen
2013-04-20 19:19 ` [PATCH 14/15] perf, x86: Add Haswell TSX event aliases v4 Andi Kleen
2013-04-20 19:19 ` [PATCH 15/15] perf, tools: Add perf stat --transaction v3 Andi Kleen
2013-06-19 8:51 ` Michael Ellerman
2013-06-19 14:46 ` Andi Kleen
2013-06-27 3:18 ` Michael Ellerman
2013-06-27 3:49 ` Andi Kleen [this message]
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=20130627034911.GO6123@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@ellerman.id.au \
--cc=mingo@elte.hu \
--cc=mlpesant@us.ibm.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