From: Peter Zijlstra <peterz@infradead.org>
To: Namhyung Kim <namhyung@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Jens Axboe <jaxboe@fusionio.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] generic-ipi: add lock context annotations
Date: Mon, 22 Nov 2010 13:46:43 +0100 [thread overview]
Message-ID: <1290430003.2072.101.camel@laptop> (raw)
In-Reply-To: <1290411232-11439-1-git-send-email-namhyung@gmail.com>
On Mon, 2010-11-22 at 16:33 +0900, Namhyung Kim wrote:
> The ipi_call_[un]lock[_irq] functions grab/release a spin lock
> but were missing proper annotations. Add it.
I really have to ask why bother? Why not add some smarts to whatever
uses these annotations?
> Signed-off-by: Namhyung Kim <namhyung@gmail.com>
> ---
> kernel/smp.c | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/kernel/smp.c b/kernel/smp.c
> index 12ed8b0..5a62f1f 100644
> --- a/kernel/smp.c
> +++ b/kernel/smp.c
> @@ -511,21 +511,25 @@ int smp_call_function(smp_call_func_t func, void *info, int wait)
> EXPORT_SYMBOL(smp_call_function);
>
> void ipi_call_lock(void)
> + __acquires(call_function.lock)
> {
> raw_spin_lock(&call_function.lock);
> }
>
> void ipi_call_unlock(void)
> + __releases(call_function.lock)
> {
> raw_spin_unlock(&call_function.lock);
> }
>
> void ipi_call_lock_irq(void)
> + __acquires(call_function.lock)
> {
> raw_spin_lock_irq(&call_function.lock);
> }
>
> void ipi_call_unlock_irq(void)
> + __releases(call_function.lock)
> {
> raw_spin_unlock_irq(&call_function.lock);
> }
next prev parent reply other threads:[~2010-11-22 12:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 7:33 [PATCH] generic-ipi: add lock context annotations Namhyung Kim
2010-11-22 12:46 ` Peter Zijlstra [this message]
2010-11-23 3:19 ` Namhyung Kim
2010-11-23 8:49 ` Jens Axboe
2010-11-23 9:40 ` Dan Carpenter
2010-11-24 5:24 ` Namhyung Kim
2010-11-24 5:43 ` Dan Carpenter
2010-11-24 14:29 ` Namhyung Kim
2010-11-24 14:33 ` Peter Zijlstra
2010-11-24 15:03 ` Namhyung Kim
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=1290430003.2072.101.camel@laptop \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=jaxboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.