From: Frederic Weisbecker <fweisbec@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
LKML <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH v2] perf: Store active software events in a hashlist
Date: Thu, 8 Apr 2010 22:11:20 +0200 [thread overview]
Message-ID: <20100408201116.GA6401@nowhere> (raw)
In-Reply-To: <1270757081.2458.4.camel@edumazet-laptop>
On Thu, Apr 08, 2010 at 10:04:41PM +0200, Eric Dumazet wrote:
> Le jeudi 08 avril 2010 à 21:39 +0200, Frederic Weisbecker a écrit :
>
> ...
>
> > @@ -5401,6 +5507,16 @@ static void __cpuinit perf_event_init_cpu(int cpu)
> > spin_lock(&perf_resource_lock);
> > cpuctx->max_pertask = perf_max_events - perf_reserved_percpu;
> > spin_unlock(&perf_resource_lock);
> > +
> > + mutex_lock(&cpuctx->hlist_mutex);
> > + if (&cpuctx->hlist_refcount > 0) {
>
>
> if (cpuctx->hlist_refcount > 0)
Doh! Thanks, will fix.
>
> > + struct swevent_hlist *hlist;
> > +
> > + hlist = kzalloc(sizeof(*hlist), GFP_KERNEL);
> > + WARN_ON_ONCE(!hlist);
> > + rcu_assign_pointer(cpuctx->swevent_hlist, hlist);
> > + }
> > + mutex_unlock(&cpuctx->hlist_mutex);
> > }
>
>
>
next prev parent reply other threads:[~2010-04-08 20:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 14:08 [PATCH] perf: Store active software events in a hashlist Frederic Weisbecker
2010-04-06 15:27 ` Peter Zijlstra
2010-04-07 9:04 ` Peter Zijlstra
2010-04-07 11:58 ` Frederic Weisbecker
2010-04-07 12:09 ` Peter Zijlstra
2010-04-08 19:39 ` [PATCH v2] " Frederic Weisbecker
2010-04-08 20:04 ` Eric Dumazet
2010-04-08 20:11 ` Frederic Weisbecker [this message]
2010-04-07 11:56 ` [PATCH] " Frederic Weisbecker
2010-04-07 11:58 ` Peter Zijlstra
2010-04-07 12:06 ` Frederic Weisbecker
2010-04-07 9:02 ` Peter Zijlstra
2010-04-07 11:52 ` Frederic Weisbecker
2010-04-07 11:56 ` Peter Zijlstra
2010-04-07 12:09 ` Frederic Weisbecker
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=20100408201116.GA6401@nowhere \
--to=fweisbec@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.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