public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Boehm, Hans" <hans_boehm@hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: ia64_cmpxchg on United Linux 1.0
Date: Tue, 30 Sep 2003 23:35:56 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106496505103304@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106496180632562@msgid-missing>

You might want to look at the atomic operations package that's included
here: http://www.hpl.hp.com/research/linux/qprof/download.php4 .

This isn't exactly a mature package, but I'm trying to get it there.
IA64 is relatively well-supported.  And AFAIK, it's the only such package
that handles memory barriers explicitly and correctly (at least by
my definition of "correctly" :-) ).

Suggestions/bug reports/patches are welcome.

Hans

> -----Original Message-----
> From: Umut Aymakoglu [mailto:umuta@us.ibm.com]
> Sent: Tuesday, September 30, 2003 3:39 PM
> To: linux-ia64@vger.kernel.org
> Subject: ia64_cmpxchg on United Linux 1.0
> 
> 
> 
> 
> 
> 
> Hi -
>    The macro used for test_and_set (ia64_cmpxchg) asm/atomic.h or
> asm/spinlock.h on United Linux 1.0 is under #ifdef _KERNEL_  
> and therefore
> can not be used in  user applications.  In RHAT 2.1 it was 
> not under #ifdef
> _KERNEL_ . Is there another macro for test_and_set  that user 
> applications
> can use?
> 
> thanks,
> Umut
> 
> -
> To unsubscribe from this list: send the line "unsubscribe 
> linux-ia64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

  reply	other threads:[~2003-09-30 23:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-30 22:38 ia64_cmpxchg on United Linux 1.0 Umut Aymakoglu
2003-09-30 23:35 ` Boehm, Hans [this message]
2003-10-01 22:12 ` Jim Wilson

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-106496505103304@msgid-missing \
    --to=hans_boehm@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