From: Peter Zijlstra <peterz@infradead.org>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, andi@firstfloor.org,
ming.m.lin@intel.com
Subject: Re: [PATCH 2/3] perf_events: fix validation of events using an extra reg (v4)
Date: Thu, 09 Jun 2011 20:40:12 +0200 [thread overview]
Message-ID: <1307644812.2497.1022.camel@laptop> (raw)
In-Reply-To: <20110606145708.GA7279@quad>
On Mon, 2011-06-06 at 16:57 +0200, Stephane Eranian wrote:
> +static struct cpu_hw_events *allocate_fake_cpuc(void)
> +{
> + struct cpu_hw_events *cpuc;
> + int cpu = smp_processor_id();
That's a boo-boo, clearly we are in a preemptible context here (see the
GFP_KERNEL allocation on the next line), so using smp_processor_id()
isn't valid.
Now since all that allocate_shared_regs() does with it is pick a NUMA
node, we should probably use raw_smp_processor_id() and leave it at
that, right?
> + cpuc = kzalloc(sizeof(*cpuc), GFP_KERNEL);
> + if (!cpuc)
> + return ERR_PTR(-ENOMEM);
> +
> + /* only needed, if we have extra_regs */
> + if (x86_pmu.extra_regs) {
> + cpuc->shared_regs = allocate_shared_regs(cpu);
> + if (!cpuc->shared_regs)
> + goto error;
> + }
> + return cpuc;
> +error:
> + free_fake_cpuc(cpuc);
> + return ERR_PTR(-ENOMEM);
> +}
next prev parent reply other threads:[~2011-06-09 18:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 14:57 [PATCH 2/3] perf_events: fix validation of events using an extra reg (v4) Stephane Eranian
2011-06-09 18:40 ` Peter Zijlstra [this message]
2011-06-09 20:36 ` Stephane Eranian
2011-06-09 20:48 ` Peter Zijlstra
2011-06-21 9:54 ` Stephane Eranian
2011-06-21 11:37 ` Peter Zijlstra
2011-07-01 15:22 ` [tip:perf/core] perf_events: Fix validation of events using an extra reg tip-bot for Stephane Eranian
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=1307644812.2497.1022.camel@laptop \
--to=peterz@infradead.org \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--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