From: Christoph Hellwig <hch@infradead.org>
To: "Zhang, Yanmin" <yanmin.zhang@intel.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org, "Pallipadi,
Venkatesh" <venkatesh.pallipadi@intel.com>,
"Shah, Rajesh" <rajesh.shah@intel.com>,
linux-ia64@vger.kernel.org
Subject: Re: [BUG] Variable stopmachine_state should be volatile
Date: Mon, 12 Dec 2005 13:39:26 +0000 [thread overview]
Message-ID: <20051212133926.GA23908@infradead.org> (raw)
In-Reply-To: <8126E4F969BA254AB43EA03C59F44E8404210E76@pdsmsx404>
> You are right. I hit the problem when I compiled kernel 2.6.9 on IA64 by intel compiler.
> cpu_relax has the compiler barrier if we use gcc, but cpu_relax becomes just ia64_hint which is null when I use intel compiler to compile kernel on ia64. file include/asm-ia64/intel_intrin.h defines ia64_hint as null.
Please report all bugs using ICC to intel. We can't and don't want to debug
this mess.
next prev parent reply other threads:[~2005-12-12 13:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 1:37 [BUG] Variable stopmachine_state should be volatile Zhang, Yanmin
2005-12-12 13:39 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-12 7:06 Zhang, Yanmin
2005-12-08 18:53 Luck, Tony
[not found] <88056F38E9E48644A0F562A38C64FB60067BE61C@scsmsx403.amr.corp.intel.com>
2005-12-02 3:53 ` Pavel Machek
2005-12-02 2:48 Zhang, Yanmin
2005-12-01 5:27 Zhang, Yanmin
2005-12-01 10:26 ` Pavel Machek
2005-12-01 2:58 Zhang, Yanmin
2005-12-01 3:25 ` Pavel Machek
2005-11-30 2:04 Zhang, Yanmin
2005-11-30 22:19 ` Pavel Machek
2005-12-02 8:04 ` Arjan van de Ven
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=20051212133926.GA23908@infradead.org \
--to=hch@infradead.org \
--cc=arjan@infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rajesh.shah@intel.com \
--cc=venkatesh.pallipadi@intel.com \
--cc=yanmin.zhang@intel.com \
/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