All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Dave Airlie <airlied@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	David Miller <davem@davemloft.net>,
	airlied@linux.ie, linux-kernel@vger.kernel.org
Subject: Re: cmpxchg is not available to generic code
Date: Mon, 23 Jul 2007 16:48:28 +1000	[thread overview]
Message-ID: <46A44F3C.5080301@yahoo.com.au> (raw)
In-Reply-To: <21d7e9970707190123n328300a6m8debe274b959ab30@mail.gmail.com>

Dave Airlie wrote:
> On 7/19/07, Andrew Morton <akpm@linux-foundation.org> wrote:
> 
>> On Thu, 19 Jul 2007 18:15:03 +1000 "Dave Airlie" <airlied@gmail.com> 
>> wrote:
>>
>> > Maybe we could add CONFIG_HAVE_CMPXCHG and let DRM depend on it..
>>
>> That would certainly be better than adding a sprinkle of architectures
>> in DRM Kconfig dependencies.
>>
>> I don't know how important DRM is on ARM.  Zero?
>>
> 
> I'd guess zero I suppose if you wanted you could hook up a PCI
> graphics card on ARM, but if you do that I think you could implement
> cmpxchg :-)

ARM does the locked load / store conditional thing which is at least as
strong as cmpxchg, so I imagine it could implement this API in kernel
and userspace quite easily if needed.

-- 
SUSE Labs, Novell Inc.

  reply	other threads:[~2007-07-23  6:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-19  7:05 cmpxchg is not available to generic code Andrew Morton
2007-07-19  7:27 ` David Miller
2007-07-19  8:15   ` Dave Airlie
2007-07-19  8:21     ` Andrew Morton
2007-07-19  8:23       ` Dave Airlie
2007-07-23  6:48         ` Nick Piggin [this message]
2007-07-19 20:54       ` David Miller
2007-07-19 20:58     ` David Miller
2007-07-19  8:02 ` Dave Airlie
2007-07-19  8:10   ` Andrew Morton
2007-07-19  8:19     ` Dave Airlie
2007-07-19  8:36       ` Andrew Morton

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=46A44F3C.5080301@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=airlied@gmail.com \
    --cc=airlied@linux.ie \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.