Re: [BUG] Variable stopmachine_state should be volatile

Hi!

> >>Those barriers should already prevent compiler optimalization, no? If
> >>they do not, just use some barriers that do.
> 
> 
> I hit the problem when compiling 2.6 kernel by intel compiler.
> How about to change the type of stopmachine_state to atomic_t?

That is certainly safest / very conservative solution.
								Pavel
-- 
Thanks, Sharp!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • RE: [BUG] Variable stopmachine_state should be volatile
    • From: "Zhang, Yanmin" <[email protected]>

• Prev by Date: [PATCH 12/12] mm: fix minor scan count bugs
• Next by Date: Re: [PATCH 01/12] vm: kswapd incmin
• Previous by thread: RE: [BUG] Variable stopmachine_state should be volatile
• Next by thread: RE: [BUG] Variable stopmachine_state should be volatile
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]