From: Andi Kleen <andi@firstfloor.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Andi Kleen <andi@firstfloor.org>,
peterz@infradead.org, linux-kernel@vger.kernel.org,
mingo@kernel.org, eranian@google.com,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 1/5] perf, x86: Remove incorrect model number from Haswell perf
Date: Wed, 27 Aug 2014 18:37:28 +0200 [thread overview]
Message-ID: <20140827163728.GQ4120@two.firstfloor.org> (raw)
In-Reply-To: <alpine.DEB.2.10.1408271144580.3323@nanos>
On Wed, Aug 27, 2014 at 11:53:57AM +0200, Thomas Gleixner wrote:
> On Wed, 27 Aug 2014, Thomas Gleixner wrote:
>
> > On Tue, 26 Aug 2014, Andi Kleen wrote:
> >
> > > > So what's the point of making the obvious onliner patch
> > > >
> > > > - case 71:
> > > >
> > > > into something which reorders the sorted case numbers?
> > >
> > > This was a merging mistake. I'll fix it to be a one liner.
> > >
> > > > And of course, this patch is missing any explanation WHY 71 is
> > > > incorrect and how it got there in the first place.
> > >
> > > 71 is a Broadwell, as you would know if you had read the next patch.
> >
> > And why on earth do I need to read the next patch to figure out what
> > the heck this patch is doing?
> >
> > Just because it's written by someone who gives a shit?
> >
> > Your unwillingness to cooperate and your advisory resistance are
> > slowly approaching the Krause level...
>
> And after reading the next patch I still can't see that 71 is a
> broadwell, because the next patch merily adds haswell names to the
> numbers. Neither of the following patches has the magic 71
> incorporated. The only model number related to broadwell is 61 in
> patch 3/5.
Ok fair enough.
It was true for v1, but not for v2.
> Try again when you figured yourself out what number means what and why
> 71 is bogus.
71 is definitely not a Haswell, but a Broadwell.
However it was removed from the Broadwell patch based on Peter's
feedback.
So technically the patch is not needed right now because there
would be no duplicates (unless 71 was readded), so the compiler
would not complain.
However it's still incorrect for Haswell, so I maintain removing
it is the right thing to do.
-Andi
next prev parent reply other threads:[~2014-08-27 16:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 22:43 Broadwell perf support Andi Kleen
2014-08-25 22:43 ` [PATCH 1/5] perf, x86: Remove incorrect model number from Haswell perf Andi Kleen
2014-08-26 21:27 ` Thomas Gleixner
2014-08-26 21:29 ` Andi Kleen
2014-08-26 22:29 ` Thomas Gleixner
2014-08-27 9:53 ` Thomas Gleixner
2014-08-27 16:37 ` Andi Kleen [this message]
2014-08-27 18:50 ` Thomas Gleixner
2014-08-25 22:43 ` [PATCH 2/5] perf, x86: Document all Haswell models Andi Kleen
2014-09-01 13:50 ` Peter Zijlstra
2014-08-25 22:43 ` [PATCH 3/5] perf, x86: Add Broadwell core support Andi Kleen
2014-09-01 13:51 ` Peter Zijlstra
2014-11-04 13:14 ` Stephane Eranian
2014-11-04 13:20 ` Peter Zijlstra
2014-08-25 22:43 ` [PATCH 4/5] perf, x86: Add INST_RETIRED.ALL workarounds Andi Kleen
2014-09-01 13:41 ` Peter Zijlstra
2014-08-25 22:43 ` [PATCH 5/5] perf, x86: Use Broadwell cache event list for Haswell Andi Kleen
2014-09-01 13:52 ` Peter Zijlstra
-- strict thread matches above, loose matches on Subject: below --
2014-09-02 18:44 [PATCH 1/5] perf, x86: Remove incorrect model number from Haswell perf Andi Kleen
2014-09-18 22:42 ` Peter Zijlstra
2014-08-27 21:03 perf, x86: Updated Broadwell patchkit Andi Kleen
2014-08-27 21:03 ` [PATCH 1/5] perf, x86: Remove incorrect model number from Haswell perf Andi Kleen
2014-08-14 1:17 Updated Broadwell perf patchkit Andi Kleen
2014-08-14 1:17 ` [PATCH 1/5] perf, x86: Remove incorrect model number from Haswell perf Andi Kleen
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=20140827163728.GQ4120@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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