All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Stephane Eranian <eranian@hpl.hp.com>
Cc: linux-kernel@vger.kernel.org, mucci@cs.utk.edu,
	linux-mips@linux-mips.org, ak@suse.de, akpm@linux-foundation.org
Subject: Re: [PATCH] MIPS: add smp_call_function_single()
Date: Fri, 27 Jul 2007 13:55:33 +0100	[thread overview]
Message-ID: <20070727125533.GD5118@linux-mips.org> (raw)
In-Reply-To: <20070727124451.GC9828@frankl.hpl.hp.com>

On Fri, Jul 27, 2007 at 05:44:51AM -0700, Stephane Eranian wrote:

> diff --git a/arch/mips/kernel/smp.c b/arch/mips/kernel/smp.c
> index be7362b..9e376e2 100644
> --- a/arch/mips/kernel/smp.c
> +++ b/arch/mips/kernel/smp.c
> @@ -193,6 +193,53 @@ void smp_call_function_interrupt(void)
>  	}
>  }
>  
> +int smp_call_function_single(int cpu, void (*func) (void *info), void *info, int retry,
> +			     int wait)
> +{
> +  struct call_data_struct data;
> +  int me = smp_processor_id();
> +
> +  /*
> +     * Can die spectacularly if this CPU isn't yet marked online
> +      */
> +  BUG_ON(!cpu_online(me));
> +  if (cpu == me) {
> +    WARN_ON(1);
> +    return -EBUSY;
> +    }
> +
> +  /* Can deadlock when called with interrupts disabled */
> +  WARN_ON(irqs_disabled());
> +
> +  data.func = func;
> +  data.info = info;
> +  atomic_set(&data.started, 0);
> +  data.wait = wait;
> +  if (wait)
> +    atomic_set(&data.finished, 0);
> +
> +  spin_lock(&smp_call_lock);
> +  call_data = &data;
> +  mb();
> +
> +  /* Send a message to the other CPU */
> +  core_send_ipi(cpu, SMP_CALL_FUNCTION);
> +
> +  /* Wait for response */
> +  /* FIXME: lock-up detection, backtrace on lock-up */
> +  while (atomic_read(&data.started) != 1)
> +    barrier();
> +
> +  if (wait)
> +    while (atomic_read(&data.finished) != 1)
> +      barrier();
> +  call_data = NULL;
> +  spin_unlock(&smp_call_lock);
> +
> +  return 0;
> +}
> +EXPORT_SYMBOL(smp_call_function_single);

Please fix the indentation to use tabs as per Documentation/CodingStyle.

>  static void stop_this_cpu(void *dummy)
>  {
>  	/*
> diff --git a/include/asm-mips/smp.h b/include/asm-mips/smp.h
> index 13aef6a..5acbf38 100644
> --- a/include/asm-mips/smp.h
> +++ b/include/asm-mips/smp.h
> @@ -102,6 +102,8 @@ static inline void smp_send_reschedule(int cpu)
>  	core_send_ipi(cpu, SMP_RESCHEDULE_YOURSELF);
>  }
>  
> +extern int smp_call_function_single(int cpuid, void (*func) (void *info),
> +				void *info, int retry, int wait);

The function is already declared in include/linux/smp.h so this segment
is unecessary.

  Ralf

  reply	other threads:[~2007-07-27 12:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-27 12:44 [PATCH] MIPS: add smp_call_function_single() Stephane Eranian
2007-07-27 12:55 ` Ralf Baechle [this message]
2007-07-27 13:53   ` Stephane Eranian
2007-07-28  9:19     ` Heiko Carstens
2007-07-29  7:33       ` Avi Kivity
2007-07-30  9:18       ` Stephane Eranian
2007-07-30  9:18         ` Stephane Eranian
  -- strict thread matches above, loose matches on Subject: below --
2007-07-30 22:01 [PATCH] MIPS: Add smp_call_function_single() pwatkins

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=20070727125533.GD5118@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=eranian@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=mucci@cs.utk.edu \
    /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.