From: "Giacomo A. Catenazzi" <cate@cateee.net>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Randy Dunlap <randy.dunlap@oracle.com>
Subject: Re: [PATCH] "volatile considered harmful" document
Date: Thu, 10 May 2007 18:14:53 +0200 [thread overview]
Message-ID: <464344FD.6000809@cateee.net> (raw)
In-Reply-To: <25493.1178744744@lwn.net>
Jonathan Corbet wrote:
> +The volatile storage class was originally meant for memory-mapped I/O
> +registers. Within the kernel, register accesses, too, should be protected
I don't think it deserves to be added in documentation, but just for
reference: in userspace "volatile" is needed in signals (posix mandates
some variables to be volatile, as API, not as funtionality). I don't
know if this was also on the original signal handling.
Anyway user space APIs are not kernel problem ;-)
ciao
cate
next prev parent reply other threads:[~2007-05-10 16:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 21:05 [PATCH] "volatile considered harmful" document Jonathan Corbet
2007-05-09 21:45 ` Jesper Juhl
2007-05-09 22:31 ` Satyam Sharma
2007-05-09 22:47 ` Jesper Juhl
2007-05-09 23:20 ` Satyam Sharma
2007-05-09 22:05 ` Heikki Orsila
2007-05-09 22:19 ` Randy Dunlap
2007-05-09 22:35 ` Scott Preece
2007-05-10 16:14 ` Giacomo A. Catenazzi [this message]
2007-05-10 19:35 ` H. Peter Anvin
2007-05-10 22:00 ` Alan Cox
2007-05-10 21:54 ` Bill Davidsen
2007-05-16 9:30 ` Thomas De Schampheleire
[not found] <fa.UIDGHS72acFv9jKylmdQQwWcXPA@ifi.uio.no>
[not found] ` <fa.fKNBJtZJWOQthlLjc1TDfY6jCLc@ifi.uio.no>
2007-05-12 18:32 ` Robert Hancock
2007-05-13 16:30 ` Krzysztof Halasa
2007-05-13 23:26 ` Bill Davidsen
2007-05-13 23:53 ` Jeff Garzik
2007-05-14 14:10 ` Bill Davidsen
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=464344FD.6000809@cateee.net \
--to=cate@cateee.net \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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 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.