mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Stephane Eranian <eranian@google.com>
Cc: Andi Kleen <andi@firstfloor.org>, "mingo@elte.hu" <mingo@elte.hu>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] perf, x86: Add workaround for MEM_*_RETIRED errata BV98
Date: Mon, 6 May 2013 21:00:24 +0200	[thread overview]
Message-ID: <20130506190024.GB17723@dyad.programming.kicks-ass.net> (raw)
In-Reply-To: <CABPqkBSqs8f9jomytPs5tyXMum1UCwSYHcTDuYwg0c-MTVvEow@mail.gmail.com>

On Mon, May 06, 2013 at 07:41:54PM +0200, Stephane Eranian wrote:

> Problem is, those events are really important. We need to be able to
> measure them.

At what cost? If the code we need to make it work is horrendous we need to
maintain that too -- possibly quite a lot longer than Intel thinks IVB is
relevant.

Anyway; since these events are immediately dangerous (they corrupt state)
blocking them is the right thing; we can always merge a patch that undoes that
once we've figured out a sane way.

Currently I'm still waiting for someone to explain (in complete detail) how the
corruption manifests. Until that is clear I can't even begin formulating what
might be needed to make it work again.

One mode that makes sense to me is where CNTx on SMTi corrupts CNTx on SMTj for
i != j. However there's also been said that the only case that doesn't corrupt
is for SMTj to have all counters disabled -- which contradicts the previous
case.

The former case we could maybe make work; the latter I can't see how we could
possible make work at all.

      reply	other threads:[~2013-05-06 19:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-29 18:45 Andi Kleen
2013-05-01  9:07 ` Peter Zijlstra
2013-05-01  9:56   ` Andi Kleen
2013-05-01 10:10     ` Ingo Molnar
2013-05-01 11:12     ` Peter Zijlstra
2013-05-01 18:13       ` Stephane Eranian
2013-05-01 19:13         ` Andi Kleen
2013-05-01 19:21           ` Stephane Eranian
2013-05-02  7:32             ` Peter Zijlstra
2013-05-06 17:41               ` Stephane Eranian
2013-05-06 19:00                 ` Peter Zijlstra [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=20130506190024.GB17723@dyad.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=andi@firstfloor.org \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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®