From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: suspend-devel@lists.sourceforge.net, pm list <linux-pm@lists.osdl.org>
Subject: Re: [RFC][PATCH -mm 1/5] PM: Make freeze_processes SMP-safe
Date: Mon, 27 Nov 2006 21:04:12 +0100 [thread overview]
Message-ID: <200611272104.13267.rjw@sisk.pl> (raw)
In-Reply-To: <20061126232858.GD13647@elf.ucw.cz>
On Monday, 27 November 2006 00:28, Pavel Machek wrote:
> Hi!
>
> > > If frozen is atomic_t, do we need memory barrier?
> >
> > I think so. For example on x86-64 atomic_read() is just a read.
>
> I'm not sure, but for x86-64 barriers are nops, anyway, IIRC.
Well, last time I checked they were "lfence" and "sfence", at least on SMP.
Greetings,
Rafael
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2006-11-27 20:04 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-25 21:10 [RFC][PATCH -mm] PM: Change ordering of suspend and resume code Rafael J. Wysocki
2006-11-25 21:29 ` [RFC][PATCH -mm 1/5] PM: Make freeze_processes SMP-safe Rafael J. Wysocki
2006-11-26 7:47 ` Pavel Machek
2006-11-26 10:02 ` Rafael J. Wysocki
2006-11-26 11:15 ` Rafael J. Wysocki
2006-11-26 13:34 ` Rafael J. Wysocki
2006-11-26 19:48 ` Pavel Machek
2006-11-26 23:09 ` Rafael J. Wysocki
2006-11-26 23:28 ` Pavel Machek
2006-11-27 2:41 ` [linux-pm] " Alan Stern
2006-11-27 20:04 ` Rafael J. Wysocki [this message]
2006-11-27 10:50 ` Pavel Machek
2006-11-27 20:02 ` Rafael J. Wysocki
2006-11-29 23:56 ` Pavel Machek
2006-11-28 23:40 ` Rafael J. Wysocki
2006-11-29 23:55 ` Pavel Machek
2006-11-30 0:21 ` Rafael J. Wysocki
2006-11-30 15:07 ` Rafael J. Wysocki
2006-11-30 15:43 ` [linux-pm] " Alan Stern
2006-11-30 16:04 ` Rafael J. Wysocki
2006-11-30 19:23 ` Rafael J. Wysocki
2006-11-30 22:34 ` Alan Stern
2006-11-30 22:57 ` Rafael J. Wysocki
2006-12-01 14:56 ` Alan Stern
2006-12-01 19:57 ` Rafael J. Wysocki
2006-12-01 21:17 ` Alan Stern
2006-12-01 21:19 ` Rafael J. Wysocki
2006-12-01 22:07 ` Alan Stern
2006-12-01 23:38 ` Rafael J. Wysocki
2006-12-02 11:55 ` Pavel Machek
2006-12-02 15:39 ` Alan Stern
2006-12-03 11:17 ` Rafael J. Wysocki
2006-11-30 21:55 ` [Suspend-devel] " Rafael J. Wysocki
2006-11-26 19:45 ` [linux-pm] " Pavel Machek
2006-11-26 23:37 ` Luca
2006-11-25 21:34 ` [RFC][PATCH -mm 2/5] swsusp: Change code ordering in disk.c Rafael J. Wysocki
2006-11-25 21:38 ` [RFC][PATCH -mm 3/5] swsusp: Change code ordering in user.c Rafael J. Wysocki
2006-11-25 21:45 ` [RFC][PATCH -mm 4/5] swsusp: Add PLATFORM_SNAPSHOT and PLATFORM_RESTORE ioctls Rafael J. Wysocki
2006-11-26 19:51 ` [linux-pm] " Pavel Machek
2006-11-26 23:12 ` Rafael J. Wysocki
2006-11-26 23:29 ` Pavel Machek
2006-11-27 10:37 ` Pavel Machek
2006-11-25 21:49 ` [RFC][PATCH -mm 5/5] PM: Change code ordering in main.c Rafael J. Wysocki
2006-11-26 7:44 ` [RFC][PATCH -mm] PM: Change ordering of suspend and resume code Pavel Machek
2006-11-26 10:08 ` Rafael J. Wysocki
2006-11-26 21:31 ` Pavel Machek
2006-11-26 23:15 ` Rafael J. Wysocki
2006-11-30 14:02 ` Stefan Seyfried
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=200611272104.13267.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-pm@lists.osdl.org \
--cc=pavel@ucw.cz \
--cc=suspend-devel@lists.sourceforge.net \
/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