public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: ia64_spinlock_contention and NEW_LOCK
Date: Thu, 13 Mar 2003 22:42:41 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709806089@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709806055@msgid-missing>

On Thu, 13 Mar 2003 14:26:28 -0800, 
David Mosberger <davidm@napali.hpl.hp.com> wrote:
>>>>>> On Fri, 14 Mar 2003 09:20:12 +1100, Keith Owens <kaos@sgi.com> said:
>
>  Keith> I am not touching the real ar.pfs, precisely to avoid
>  Keith> changing leaf routines.  Setting r29 to 0 and .save ar.pfs,
>  Keith> r29 in ia64_unwind_contention will fool the unwind code into
>  Keith> doing the unwind correctly but without changing the state of
>  Keith> the routine using spin_lock().
>
>Ah, sorry, I didn't read your mail carefully enough.  Hmmh, not
>exactly a pretty solution, but I don't see anything obviously wrong
>with it either.  With libunwind, you could in fact say
>
>	.save ar.pfs,r0
>
>but I don't remember whether this would work with the kernel unwinder
>(if it doesn't, it would be easy to fix though).

I wanted to do .save ar.pfs,r0, but it needs a change to
unw_access_gr().  As you say, easy enough to fix, but I wanted to
minimize the changes for this new spinlock code.  OTOH, if you do not
mind changing unw_access_gr(), I will do it that way and free up r29.



  parent reply	other threads:[~2003-03-13 22:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-12 10:19 [Linux-ia64] Re: ia64_spinlock_contention and NEW_LOCK Keith Owens
2003-03-12 10:35 ` Keith Owens
2003-03-12 17:27 ` David Mosberger
2003-03-12 21:18 ` Keith Owens
2003-03-12 21:51 ` Keith Owens
2003-03-13 19:16 ` David Mosberger
2003-03-13 21:59 ` Keith Owens
2003-03-13 22:14 ` David Mosberger
2003-03-13 22:20 ` Keith Owens
2003-03-13 22:26 ` David Mosberger
2003-03-13 22:42 ` Keith Owens [this message]
2003-03-13 22:46 ` David Mosberger

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=marc-linux-ia64-105590709806089@msgid-missing \
    --to=kaos@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