From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Converting ia64 kernel unwinder to lock free code
Date: Fri, 22 Oct 2004 07:30:39 +0000 [thread overview]
Message-ID: <16760.46879.296371.725336@napali.hpl.hp.com> (raw)
In-Reply-To: <5907.1098419155@kao2.melbourne.sgi.com>
>>>>> On Fri, 22 Oct 2004 14:25:55 +1000, Keith Owens <kaos@sgi.com> said:
Keith> Before I start on this task, are there any other plans for
Keith> the kernel unwinder code? In the past davidm has hinted at
Keith> replacing it with libunwind.
I definitely want to do that. I'm not sure you can make it entirely
lock-free with caching enabled, but libunwind already works such that
if the lock is already taken, it bypasses the cache and hence doesn't
need to acquire the lock.
--david
prev parent reply other threads:[~2004-10-22 7:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 4:25 Converting ia64 kernel unwinder to lock free code Keith Owens
2004-10-22 7:30 ` David Mosberger [this message]
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=16760.46879.296371.725336@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.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