mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: tip-bot for Adrian Hunter <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: hpa@zytor.com, linux-kernel@vger.kernel.org,
	adrian.hunter@intel.com, tglx@linutronix.de, acme@redhat.com,
	mingo@kernel.org
Subject: [tip:perf/urgent] perf intel-pt: Fix MTC timing after overflow
Date: Thu, 7 Jun 2018 01:23:08 -0700	[thread overview]
Message-ID: <tip-dd27b87ab5fcf3ea1c060b5e3ab5d31cc78e9f4c@git.kernel.org> (raw)
In-Reply-To: <1527762225-26024-4-git-send-email-adrian.hunter@intel.com>

Commit-ID:  dd27b87ab5fcf3ea1c060b5e3ab5d31cc78e9f4c
Gitweb:     https://git.kernel.org/tip/dd27b87ab5fcf3ea1c060b5e3ab5d31cc78e9f4c
Author:     Adrian Hunter <adrian.hunter@intel.com>
AuthorDate: Thu, 31 May 2018 13:23:44 +0300
Committer:  Arnaldo Carvalho de Melo <acme@redhat.com>
CommitDate: Wed, 6 Jun 2018 12:52:08 -0300

perf intel-pt: Fix MTC timing after overflow

On some platforms, overflows will clear before MTC wraparound, and there
is no following TSC/TMA packet. In that case the previous TMA is valid.
Since there will be a valid TMA either way, stop setting 'have_tma' to
false upon overflow.

Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
Cc: stable@vger.kernel.org
Link: http://lkml.kernel.org/r/1527762225-26024-4-git-send-email-adrian.hunter@intel.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
 tools/perf/util/intel-pt-decoder/intel-pt-decoder.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/tools/perf/util/intel-pt-decoder/intel-pt-decoder.c b/tools/perf/util/intel-pt-decoder/intel-pt-decoder.c
index e5eb91777383..881d7c5e5e2a 100644
--- a/tools/perf/util/intel-pt-decoder/intel-pt-decoder.c
+++ b/tools/perf/util/intel-pt-decoder/intel-pt-decoder.c
@@ -1376,7 +1376,6 @@ static int intel_pt_overflow(struct intel_pt_decoder *decoder)
 {
 	intel_pt_log("ERROR: Buffer overflow\n");
 	intel_pt_clear_tx_flags(decoder);
-	decoder->have_tma = false;
 	decoder->cbr = 0;
 	decoder->timestamp_insn_cnt = 0;
 	decoder->pkt_state = INTEL_PT_STATE_ERR_RESYNC;

  reply	other threads:[~2018-06-07  8:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-31 10:23 [PATCH 0/4] perf intel-pt: Fixes Adrian Hunter
2018-05-31 10:23 ` [PATCH 1/4] perf intel-pt: Fix sync_switch INTEL_PT_SS_NOT_TRACING Adrian Hunter
2018-06-07  8:22   ` [tip:perf/urgent] " tip-bot for Adrian Hunter
2018-05-31 10:23 ` [PATCH 2/4] perf intel-pt: Fix decoding to accept CBR between FUP and corresponding TIP Adrian Hunter
2018-06-07  8:22   ` [tip:perf/urgent] " tip-bot for Adrian Hunter
2018-05-31 10:23 ` [PATCH 3/4] perf intel-pt: Fix MTC timing after overflow Adrian Hunter
2018-06-07  8:23   ` tip-bot for Adrian Hunter [this message]
2018-05-31 10:23 ` [PATCH 4/4] perf intel-pt: Fix "Unexpected indirect branch" error Adrian Hunter
2018-06-07  8:23   ` [tip:perf/urgent] " tip-bot for Adrian Hunter
2018-06-05 15:32 ` [PATCH 0/4] perf intel-pt: Fixes Arnaldo Carvalho de Melo

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=tip-dd27b87ab5fcf3ea1c060b5e3ab5d31cc78e9f4c@git.kernel.org \
    --to=tipbot@zytor.com \
    --cc=acme@redhat.com \
    --cc=adrian.hunter@intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®