public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Val Henson <val@nmt.edu>
To: Paul Mackerras <paulus@samba.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: smp_send_reschedule vs. smp_migrate_task
Date: Thu, 14 Feb 2002 22:55:54 -0700	[thread overview]
Message-ID: <20020214225554.K1557@boardwalk> (raw)
In-Reply-To: <15466.6058.686853.295549@argo.ozlabs.ibm.com> <20020214150331.P30586@boardwalk> <15468.14888.334751.716019@argo.ozlabs.ibm.com>
In-Reply-To: <15468.14888.334751.716019@argo.ozlabs.ibm.com>; from paulus@samba.org on Fri, Feb 15, 2002 at 09:28:56AM +1100

On Fri, Feb 15, 2002 at 09:28:56AM +1100, Paul Mackerras wrote:
> Val Henson writes:
> 
> > I had only one IPI for the RPIC (an interrupt controller only used on
> > Synergy PPC boards) and I implemented a little message queue to
> > simulate all 4 IPI's.  The mailbox implementation suggested by James
> > Bottomley ended up having race conditions on our board.  It's probably
> > not the most elegant solution, but it works and required no change to
> > the PowerPC SMP code.  See my "Make Gemini boot" patch to linuxppc-dev
> > and take a look at the files rpic.c and rpic.h.
> 
> In that post I was really asking the following questions:
> 
> * how often does smp_send_reschedule get called?
> * how often does smp_migrate_task get called?
> * if smp_send_reschedule and smp_migrate_task were mutually exclusive,
>   i.e. both used the same spinlock, could that lead to deadlock?
> 
> James Bottomley answered the first two for me but not the third.

Understood.

I'm still a little disgusted by a system that works for 4
smp_<whatever> functions but not 5. :)

-VAL

  reply	other threads:[~2002-02-15  5:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-13  7:37 smp_send_reschedule vs. smp_migrate_task Paul Mackerras
2002-02-14 22:03 ` Val Henson
2002-02-14 22:28   ` Paul Mackerras
2002-02-15  5:55     ` Val Henson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-14 23:24 James Bottomley

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=20020214225554.K1557@boardwalk \
    --to=val@nmt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --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