public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Robin Holt <holt@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC] Convert ia64 spinlocks to use "tickets"
Date: Sat, 12 Sep 2009 07:59:53 +0000	[thread overview]
Message-ID: <20090912075953.GA8934@sgi.com> (raw)
In-Reply-To: <4aa9e16649286264@agluck-desktop.sc.intel.com>

On Thu, Sep 10, 2009 at 10:34:30PM -0700, Luck, Tony wrote:
...
> -static inline void
> -__raw_spin_lock_flags (raw_spinlock_t *lock, unsigned long flags)
> +static __always_inline void __ticket_spin_lock(raw_spinlock_t *lock)
>  {
> -	register volatile unsigned int *ptr asm ("r31") = &lock->lock;
> -
> -#if (__GNUC__ = 3 && __GNUC_MINOR__ < 3)
> -# ifdef CONFIG_ITANIUM
> -	/* don't use brl on Itanium... */
> -	asm volatile ("{\n\t"
> -		      "  mov ar.ccv = r0\n\t"
> -		      "  mov r28 = ip\n\t"
> -		      "  mov r30 = 1;;\n\t"
> -		      "}\n\t"
> -		      "cmpxchg4.acq r30 = [%1], r30, ar.ccv\n\t"
> -		      "movl r29 = ia64_spinlock_contention_pre3_4;;\n\t"
...
> -		      "(p14) brl.call.spnt.many b6=ia64_spinlock_contention;;"

Have you done any testing where the spin with interrupts disabled was
problematic?

I know we have had ages of problems with these, but I don't recall
any specific instances right now (keep in mind it is 3:00 AM when I am
finally getting to look at this).

Thanks,
Robin

  parent reply	other threads:[~2009-09-12  7:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-11  5:34 [RFC] Convert ia64 spinlocks to use "tickets" Luck, Tony
2009-09-11 16:47 ` Rick Jones
2009-09-11 22:22 ` Luck, Tony
2009-09-12  7:59 ` Robin Holt [this message]
2009-09-12 21:23 ` Andi Kleen
2009-09-12 23:24 ` Luck, Tony
2009-09-12 23:39 ` Luck, Tony

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=20090912075953.GA8934@sgi.com \
    --to=holt@sgi.com \
    --cc=linux-ia64@vger.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