public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: markus.t.metzger@intel.com
Cc: mingo@redhat.com, mingo@elte.hu, linux-kernel@vger.kernel.org,
	Mark Kettenis <kettenis@gnu.org>, Pedro Alves <palves@redhat.com>,
	Jan Kratochvil <jan.kratochvil@redhat.com>,
	gdb-patches@sourceware.org
Subject: Re: [PATCH] x86, perf, bts: disable BTS from Nehalem to Ivy Bridge
Date: Thu, 24 Jan 2013 16:46:37 +0100	[thread overview]
Message-ID: <20130124154637.GB32146@gmail.com> (raw)
In-Reply-To: <1354876511-25294-1-git-send-email-markus.t.metzger@intel.com>


* markus.t.metzger@intel.com <markus.t.metzger@intel.com> wrote:

> From: Markus Metzger <markus.t.metzger@intel.com>
> 
> Starting with Nehalem, the BTS "from" information may in some cases be
> incorrect (AAJ122).
> 
> This has been detected while adding branch tracing support to gdb, where it
> results in sporadic test fails.
> 
> Disable BTS support on Nehalem, Westmere, Sandy Bridge, and Ivy Bridge.

But the failures are rare, so the BTS data is still correct 
statistically, by and large, right? So why not just keep it 
as-is and teach tooling to be more robust about implausible 
trace entries? It has to be ready for that eventuality *anyway*.

Thanks,

	Ingo

  reply	other threads:[~2013-01-24 15:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-07 10:35 [PATCH] x86, perf, bts: disable BTS from Nehalem to Ivy Bridge markus.t.metzger
2013-01-24 15:46 ` Ingo Molnar [this message]
2013-01-24 16:17   ` Metzger, Markus T

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=20130124154637.GB32146@gmail.com \
    --to=mingo@kernel.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=kettenis@gnu.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus.t.metzger@intel.com \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=palves@redhat.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