From: Andi Kleen <ak@suse.de>
To: Suleiman Souhlal <ssouhlal@freebsd.org>
Cc: Shem Multinymous <multinymous@gmail.com>,
Linux Kernel ML <linux-kernel@vger.kernel.org>,
vojtech@suse.cz, Jiri Bohac <jbohac@suse.cz>,
Nigel Cunningham <ncunningham@cyclades.com>,
Pavel Machek <pavel@suse.cz>
Subject: Re: [PATCH 0/2] Make the TSC safe to be used by gettimeofday().
Date: Tue, 14 Nov 2006 19:30:17 +0100 [thread overview]
Message-ID: <200611141930.17860.ak@suse.de> (raw)
In-Reply-To: <4559F781.6020607@FreeBSD.org>
> I have to admit that I didn't really design this patch with
> suspend/resume in mind, and that I'm not too familiar with how they work.
>
> Do the HPET/ACPI timers still run while the system is suspended?
No. In suspend to RAM only the RAM is still powered. On suspend to disk
everything is off. But you can do every needed synchronization on resume.
-Andi
next prev parent reply other threads:[~2006-11-14 18:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 1:06 [PATCH 0/2] Make the TSC safe to be used by gettimeofday() Suleiman Souhlal
2006-11-14 1:08 ` [PATCH 1/2] " Suleiman Souhlal
2006-11-14 2:05 ` Andi Kleen
2006-11-14 2:25 ` Suleiman Souhlal
2006-11-14 2:44 ` Andi Kleen
2006-11-14 3:35 ` dean gaudet
2006-11-14 4:22 ` dean gaudet
2006-11-14 3:54 ` Suleiman Souhlal
2006-11-14 11:12 ` Andi Kleen
2006-11-14 1:09 ` [PATCH 2/2] Introduce a vmonotonic_clock() vsyscall Suleiman Souhlal
2006-11-14 1:50 ` [PATCH 0/2] Make the TSC safe to be used by gettimeofday() Andi Kleen
2006-11-14 2:06 ` Suleiman Souhlal
2006-11-14 11:10 ` [PATCH 0/2] Make the TSC safe to be used by gettimeofday() II Andi Kleen
2006-11-14 12:30 ` [PATCH 0/2] Make the TSC safe to be used by gettimeofday() Shem Multinymous
2006-11-14 17:06 ` Suleiman Souhlal
2006-11-14 18:30 ` Andi Kleen [this message]
2006-11-14 21:28 ` Christoph Lameter
2006-11-14 7:42 ` 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=200611141930.17860.ak@suse.de \
--to=ak@suse.de \
--cc=jbohac@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=multinymous@gmail.com \
--cc=ncunningham@cyclades.com \
--cc=pavel@suse.cz \
--cc=ssouhlal@freebsd.org \
--cc=vojtech@suse.cz \
/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