From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: Benjamin Herrenschmidt
<benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
Cc: Linux-pm mailing list <linux-pm-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: comments on irc log
Date: Fri, 18 Mar 2005 19:13:17 +0100 [thread overview]
Message-ID: <20050318181317.GD18427@elf.ucw.cz> (raw)
In-Reply-To: <1111113131.25179.73.camel@gaston>
[-- Attachment #1: Type: text/plain, Size: 2575 bytes --]
Hi!
> I've browsed the IRC log and have a few notes/comments/replies:
>
> 21:38:01< pavelm> At one point someone at intel was looking onto s-t-ram on smp machine...
> 21:38:13< pavelm> ...is he/she still working on that?
> 21:38:51< pavelm> Airplane-like machine was toshiba laptop; I did nnot open it.
> 21:39:24< pavelm> DC=dual core... aha, I parsed it wrong.
>
> Pavel: Paulus has that working on an SMP PowerMac. The simplest/safest way to do that
> is to implement some kind of hotplug CPU (even if the CPU isn't physically turned off,
> just "park" it in some kind of sleep loop or so), and only trigger the system-wide STR
> after you have stopped all CPUs but one. He left usrland the
> responsibility to do that.
I do not want to leave that to userland, because we need it during
swsusp resume, too, and userland is not available at that
point. Otherwise I agree (and have some code from Li that implements
it that way).
> 21:43:34< nigel> Luming: I was meaning one where the chip itself gets completely powered down and needs a complete reconfigure on wake.
> 21:43:39< pavelm> ;-< well, when BIOS at least posts the card, things are easy.
>
> Note that I have some code for POST'ing some radeon's that might be adapt-able. The only
> "issue" is I don't know how to extract from the x86 BIOS ROM the proper sequence of values
> for the SDRAM mode register (SDRAM chip init). This is write-only obviously so I can't just
> read the values before sleep and POST the chip with those like I do for the rest of the
> chip. I know values for Mac laptops, not x86.
So it is basically "need very simple piece of documentation from
notebook vendor" and some vendors are already wiling to share that
info? Good.
> 21:52:11< pavelm> I was playing with variable scheduling ticks here, hoping to save some power.
> 21:52:31< pavelm> How big power savings should I expect?
> 21:52:48< pavelm> What cpu will benefit most?
> 21:53:04< pavelm> Is there easy way to measure it?
>
> I played with that too on some PPCs and was surprised by the absence of benefit, but I might
> have done something wrong, I need to instrument the stuff better.
Difference between HZ=100 and HZ=1000 was measuerd to be approx. as
big as disk spinnned up vs. spinned down (i.e. watt or so) by
seife.... Not *that* unimportant. But it took month or so to get that
data, because he was basically measuring runtime from full to empty
battery.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2005-03-18 18:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-18 2:32 comments on irc log Benjamin Herrenschmidt
2005-03-18 16:56 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.0503181147110.1099-100000-3WpdWqXrU/qjv4eRiOYp3g@public.gmane.org>
2005-03-18 18:14 ` Pavel Machek
2005-03-18 23:07 ` Benjamin Herrenschmidt
2005-03-18 23:18 ` Pavel Machek
[not found] ` <20050318231801.GE24449-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-03-19 1:21 ` Benjamin Herrenschmidt
2005-03-19 3:23 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.0503182205040.30560-100000-pYrvlCTfrz9XsRXLowluHWD2FQJk+8+b@public.gmane.org>
2005-03-19 10:33 ` Pavel Machek
[not found] ` <20050319103351.GM24449-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-03-19 15:49 ` Alan Stern
2005-03-19 12:02 ` Benjamin Herrenschmidt
2005-03-19 10:32 ` Pavel Machek
2005-03-18 18:13 ` Pavel Machek [this message]
[not found] ` <20050318181317.GD18427-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-03-18 23:15 ` Benjamin Herrenschmidt
2005-03-21 20:06 ` Jordan Crouse
[not found] ` <20050321130612.135d726e-aftB2sG12IhaqnLngUycEA@public.gmane.org>
2005-03-21 20:03 ` Pavel Machek
2005-03-23 19:46 ` David Brownell
[not found] ` <200503231146.17105.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2005-03-23 19:53 ` David Brownell
[not found] ` <200503231153.48230.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2005-03-23 20:16 ` Todd Poynor
[not found] ` <4241CE9B.5050604-Igf4POYTYCDQT0dZR+AlfA@public.gmane.org>
2005-03-23 20:46 ` David Brownell
[not found] ` <200503231246.05656.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2005-03-24 1:57 ` Todd Poynor
2005-03-23 21:08 ` Pavel Machek
[not found] ` <20050323210835.GF30704-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-03-23 21:33 ` David Brownell
[not found] ` <200503231333.22647.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2005-03-23 21:53 ` Pavel Machek
[not found] ` <20050323215330.GJ30704-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-03-24 18:40 ` Patrick Mochel
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=20050318181317.GD18427@elf.ucw.cz \
--to=pavel-+zi9xunit7i@public.gmane.org \
--cc=benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org \
--cc=linux-pm-qjLDD68F18O7TbgM5vRIOg@public.gmane.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