From: Thomas Gleixner <tglx@linutronix.de>
To: Vikas Shivappa <vikas.shivappa@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
x86@kernel.org, Stephane Eranian <eranian@google.com>,
Matt Fleming <matt@codeblueprint.co.uk>
Subject: Re: [PATCH] x86/perf/intel/cqm: Get rid of the silly for_each_cpu lookups
Date: Wed, 17 Feb 2016 19:35:56 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.11.1602171934590.19512@nanos> (raw)
In-Reply-To: <alpine.DEB.2.11.1602171929210.19512@nanos>
On Wed, 17 Feb 2016, Thomas Gleixner wrote:
> On Wed, 17 Feb 2016, Vikas Shivappa wrote:
> > > - cpumask_set_cpu(cpu, &cqm_cpumask);
> > > + /* First online cpu in package becomes the reader */
> > > + reader = cpumask_any_and(topology_core_cpumask(cpu), &cqm_cpumask);
> > > + if (reader >= nr_cpu_ids)
> > > + cpumask_set_cpu(cpu, &cqm_cpumask);
> >
> > I was confused by the topology_core_cpumask naming as its really the mask of
> > all cpus in the same package. I sent a patch for cqm and rapl to fix this
> > looping when you had given the same feedback during CAt patches review , but
> > they have never made it so far due to CAT patch issues.
>
> Duh, totally forgot about them.
>
> > Would it be better to resend the rapl (looks like perf_uncore has same loop)
> > fixes separately ?
>
> Yes, please resend the rapl one. perf_uncore is a different trainwreck which I
> fixed already:
>
> lkml.kernel.org/r/20160217132903.767990400@linutronix.de
And looking at rapl, it's the same trainwreck as uncore versus error
handling. Sigh....
Thanks,
tglx
next prev parent reply other threads:[~2016-02-17 18:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 15:47 Thomas Gleixner
2016-02-17 16:08 ` Thomas Gleixner
2016-02-17 16:28 ` Matt Fleming
2016-02-17 18:27 ` Vikas Shivappa
2016-02-17 18:31 ` Thomas Gleixner
2016-02-17 18:35 ` Thomas Gleixner [this message]
2016-02-17 18:48 ` Vikas Shivappa
2016-02-17 19:09 ` Thomas Gleixner
2016-02-18 20:15 ` Thomas Gleixner
2016-02-18 23:12 ` Vikas Shivappa
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=alpine.DEB.2.11.1602171934590.19512@nanos \
--to=tglx@linutronix.de \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=peterz@infradead.org \
--cc=vikas.shivappa@intel.com \
--cc=x86@kernel.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®