From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Chase Venters <chase.venters@clientec.com>,
Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] remove volatile from nmi.c
Date: Fri, 14 Jul 2006 13:00:51 -0400 [thread overview]
Message-ID: <1152896451.27135.16.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0607140941170.5623@g5.osdl.org>
On Fri, 2006-07-14 at 09:47 -0700, Linus Torvalds wrote:
>
> So I'd argue that it's actually _worse_ to do a "mindless" conversion away
> from volatile, than it is to just remove them outright. Removing them
> outright may show a bug that the volatile hid (and at that point, people
> may see what the _deeper_ problem was), but at least it won't add a memory
> barrier that isn't necessary and will potentially just confuse people.
Perfectly agree, and that is why in my post I said this was a learning
experience for me and to please review. Thinking, at worst you guys
just tell me I'm completely wrong. At best I find a real bug and have a
fix for it. Seems I'm in between the two ;)
I believe I did find a real bug (just luck that it worked) but as you
say, my fix is wrong and if applied would hide the bug. So this was to
bring attention to would be bugs, and in the mean time, I learn exactly
how to use memory barriers and how to get rid of volatiles. Yes, this
was more of a blind change, and I should have looked more into exactly
what the code was doing. But this was more to bring attention to a
problem area than really to solve it.
Thanks for responding and giving me a lesson :)
-- Steve
next prev parent reply other threads:[~2006-07-14 17:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-14 13:04 [PATCH] remove volatile from nmi.c Steven Rostedt
2006-07-14 13:28 ` Nick Piggin
2006-07-14 15:23 ` Linus Torvalds
2006-07-14 16:32 ` Chase Venters
2006-07-14 16:47 ` Linus Torvalds
2006-07-14 17:00 ` Steven Rostedt [this message]
2006-07-14 17:28 ` Linus Torvalds
2006-07-14 17:38 ` Steven Rostedt
2006-07-14 17:41 ` Linus Torvalds
2006-07-14 17:58 ` Andrew Morton
2006-07-14 20:04 ` [PATCH 00/02] remove set_wmb Steven Rostedt
2006-07-14 20:05 ` [PATCH 01/02] remove set_wmb - doc update Steven Rostedt
2006-07-15 2:22 ` Matthew Wilcox
2006-07-15 2:35 ` Steven Rostedt
2006-07-14 20:05 ` [PATCH 02/02] remove set_wmb - arch removal Steven Rostedt
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=1152896451.27135.16.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=akpm@osdl.org \
--cc=chase.venters@clientec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@osdl.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