public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Tejun Heo <tj@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH hw_breakpoint] percpu: add __percpu sparse annotations to hw_breakpoint
Date: Wed, 17 Feb 2010 17:39:49 +0100	[thread overview]
Message-ID: <20100217163944.GC5041@nowhere> (raw)
In-Reply-To: <4B7B4B7A.9050902@kernel.org>

On Wed, Feb 17, 2010 at 10:50:50AM +0900, Tejun Heo wrote:
> Add __percpu sparse annotations to hw_breakpoint.
> 
> These annotations are to make sparse consider percpu variables to be
> in a different address space and warn if accessed without going
> through percpu accessors.  This patch doesn't affect normal builds.
> 
> In kernel/hw_breakpoint.c, per_cpu(nr_task_bp_pinned, cpu)'s will
> trigger sprious noderef related warnings from sparse.  Changing it to
> &per_cpu(nr_task_bp_pinned[0], cpu) will work around the problem but
> deemed to ugly by the maintainer.  Leave it alone until better
> solution can be found.
> 
> Signed-off-by: Tejun Heo <tj@kernel.org>
> Cc: Frederic Weisbecker <fweisbec@gmail.com>
> ---
> Frederic, can you please put this into the tree for hw_breakpoint?
> 
> Thanks.


Yeah, looks good, I'm queuing it.
Just few comments below, for nano-considerations.



>  	cpu_events = alloc_percpu(typeof(*cpu_events));
>  	if (!cpu_events)
> -		return ERR_PTR(-ENOMEM);
> +		return (void __percpu __force *)ERR_PTR(-ENOMEM);



Is this pattern common enough that we can think about a ERR_CPU_PTR ?




>  	sample_hbp = register_wide_hw_breakpoint(&attr, sample_hbp_handler);
> -	if (IS_ERR(sample_hbp)) {
> -		ret = PTR_ERR(sample_hbp);
> +	if (IS_ERR((void __force *)sample_hbp)) {
> +		ret = PTR_ERR((void __force *)sample_hbp);


Same comments here, although I wouldn't like much a CPU_PTR_ERR or
IS_ERR_CPU.... CPP is just so poor in magic for that.

I must confess I miss a bit the old per_cpu prefix that guarded the implicit
separate namespace.

Anyway, I'm queuing it, thanks.


  reply	other threads:[~2010-02-17 16:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17  1:50 [PATCH hw_breakpoint] percpu: add __percpu sparse annotations to hw_breakpoint Tejun Heo
2010-02-17 16:39 ` Frederic Weisbecker [this message]
2010-02-18  0:49   ` Tejun Heo
2010-02-18 18:25     ` Frederic Weisbecker
2010-02-28  8:57 ` [tip:perf/core] percpu: Add " tip-bot for Tejun Heo

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=20100217163944.GC5041@nowhere \
    --to=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tj@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