mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	mingo@elte.hu, eranian@google.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf, x86: Add workaround for MEM_*_RETIRED errata BV98
Date: Wed, 1 May 2013 12:10:04 +0200	[thread overview]
Message-ID: <20130501101004.GA17360@gmail.com> (raw)
In-Reply-To: <m261z3uipb.fsf@firstfloor.org>


* Andi Kleen <andi@firstfloor.org> wrote:

> Peter Zijlstra <peterz@infradead.org> writes:
> >
> > So you're saying that if two SMT siblings count the same MEM_*_RETIRED event
> > (on the same counter?) events can get accounted to the wrong sibling?
> 
> It can happen regardless of what event is enabled on the other counter.
> 
> > And when the other sibling doesn't have (the same counter?) enabled we
> > can loose events?
> 
> doesn't have any events enabled.
> 
> > This begs the question what happens when the sibling does have the (same?)
> > counter enabled but counting an all together different event; do we then still
> > 'loose' events from the one sibling and add then to the other counter?
> 
> Yes, that is what the patch fixes.
> 
> Of course only if you actually apply it, and not lose it as usual.

If your snide remark is referring to your pending Haswell patchset then 
you are dead wrong: the reason why they have not been picked up yet is not 
because they were ignored, but because they had to go through 11 review 
iterations already - still counting (!).

That is a huge amount of overhead on the maintainer side.

With such a negative track record you should not expect maintainers to 
fast-track your patches or trust your judgement too much - your patches 
are often sloppy, your changelogs incomplete or outright deceiving, your 
replies are often evasive and non-constructive.

Thanks,

	Ingo

  reply	other threads:[~2013-05-01 10:10 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 [this message]
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

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=20130501101004.GA17360@gmail.com \
    --to=mingo@kernel.org \
    --cc=andi@firstfloor.org \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    /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®