All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: "Jan Beulich" <JBeulich@novell.com>
Cc: "Ingo Molnar" <mingo@elte.hu>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Nick Piggin" <npiggin@suse.de>, <hpa@zytor.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: uses of cmpxchg/xadd in spinlock.h and rwsem.h vs. CONFIG_M386
Date: Tue, 12 May 2009 18:18:37 +0200	[thread overview]
Message-ID: <m2vdo6l2g2.fsf@igel.home> (raw)
In-Reply-To: <4A09AF8402000078000007DC@vpn.id2.novell.com> (Jan Beulich's message of "Tue, 12 May 2009 16:19:00 +0100")

"Jan Beulich" <JBeulich@novell.com> writes:

> While looking at a completely different issue I happened to grep for uses of
> xadd, and it would appear to me that there got uses added that would make
> a M386-configured SMP kernel die on an actual i386.
>
> Oh, for the rwsem case I see - it would use the RWSEM_GENERIC_SPINLOCK case
> when selecting M386. But I see nothing similar for the ticket spinlocks - am
> I overlooking something?

This came up before, see
<http://marc.info/?l=linux-kernel&m=123141659309208&w=2>.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

      parent reply	other threads:[~2009-05-12 16:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-12 15:19 uses of cmpxchg/xadd in spinlock.h and rwsem.h vs. CONFIG_M386 Jan Beulich
2009-05-12 15:37 ` Nick Piggin
2009-05-12 15:57   ` Alan Cox
2009-05-12 16:02   ` Peter Zijlstra
2009-05-12 15:51 ` H. Peter Anvin
2009-05-12 15:57   ` Nick Piggin
2009-05-12 16:04     ` H. Peter Anvin
2009-05-12 16:16       ` Jan Beulich
2009-05-12 16:18 ` Andreas Schwab [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=m2vdo6l2g2.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=JBeulich@novell.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=npiggin@suse.de \
    --cc=tglx@linutronix.de \
    /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.