From: "chaitanya Huilgol" <chaitanya@tidaldata.com>
To: <linux-kernel@vger.kernel.org>
Subject: FW: cmpxchg hard lockup on AMD64 - ASUS(A8V-MX)
Date: Mon, 22 May 2006 13:29:52 +0530 [thread overview]
Message-ID: <007a01c67d75$b627b8e0$40c8720a@Everest> (raw)
I am seeing a hard lockup when the lock-free lifo
implementation below is run on a AMD Athlon 64
and ASUS A8V-MX motherboard. GCC version is
gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-47.fc4)
I have run this code on Pentiums without any issue
till now. Also the same code works fine in userland.
I fail to understand as to why the problem occurs
only in kernel mode.
Thanks,
Chaitanya
http://lalists.stanford.edu/lad/2000/Jul/0319.html
#ifdef __SMP__
#define LOCK "lock ; "
#else
#define LOCK ""
#endif
typedef struct cell {
struct cell* link; /* next cell in the lifo */
/*...*/ /* any data here */
} cell;
typedef struct lifo {
volatile cell* top; /* top of the stack */
volatile unsigned long cnt; /* used to avoid ABA problem */
} lifo;
void init(lifo* lf)
{
lf->top = 0;
lf->cnt = 0;
}
void push (lifo * lf, cell * cl)
{
__asm__ __volatile__ (
"# LFPUSH \n\t"
"1:\t"
"movl %2, (%1) \n"
LOCK "cmpxchg %1, %0 \n\t"
"jnz 1b \n\t"
:
:"m" (*lf), "r" (cl), "a" (lf->top)
);
}
cell* pop (lifo * lf)
{
cell* v=0;
__asm__ __volatile__ (
"# LFPOP \n\t"
"testl %%eax, %%eax \n\t"
"jz 20f \n"
"10:\t"
"movl (%%eax), %%ebx \n\t"
"movl %%edx, %%ecx \n\t"
"incl %%ecx \n\t"
LOCK "cmpxchg8b %1 \n\t"
"jz 20f \n\t"
"testl %%eax, %%eax \n\t"
"jnz 10b \n"
"20:\t"
:"=a" (v)
:"m" (*lf), "a" (lf->top), "d" (lf->cnt)
:"ecx", "ebx" );
return v;
}
next reply other threads:[~2006-05-22 7:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 7:59 chaitanya Huilgol [this message]
2006-05-22 11:12 ` FW: cmpxchg hard lockup on AMD64 - ASUS(A8V-MX) Andi Kleen
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='007a01c67d75$b627b8e0$40c8720a@Everest' \
--to=chaitanya@tidaldata.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox