From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Colin Leroy <colin@colino.net>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: TEST: Sleep patch #6
Date: Wed, 01 Dec 2004 20:22:03 +1100 [thread overview]
Message-ID: <1101892923.5593.17.camel@gaston> (raw)
In-Reply-To: <20041201101130.05f71600@pirandello>
On Wed, 2004-12-01 at 10:11 +0100, Colin Leroy wrote:
> On 01 Dec 2004 at 20h12, Benjamin Herrenschmidt wrote:
>
> Hi,
>
> > > Compiling that. btw, you didn't add the "&& !wol" before sungem's suspend call...
> >
> > What do you mean ? the whole code block is now in !wol...
>
> I'm just being stupid, i didn't see that :)
> So much for trying to read patches before having had my coffee...
>
> > Note that I'm still having problems with the cache ... I'm asking
> > Moto/Freescale...
>
> With which CPUs? I did notice zero problems with patch #5 (without freq scaling).
On my 7455 rev 3.3 at least. cpufreq on mine uses the PMU as well, thus
approx. the same code path as sleep. By doing freq. switches in a loop
from a shell script, I can make it crash in a few iterations. It seem to
be solid if I add an ugly displacement flush before the cache flush
code, but that should not be necessary and thus makes me think something
is wrong with the code.
Ben.
next prev parent reply other threads:[~2004-12-01 9:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 5:03 TEST: Sleep patch #6 Benjamin Herrenschmidt
2004-12-01 7:36 ` Colin Leroy
2004-12-01 9:05 ` Benjamin Herrenschmidt
2004-12-01 9:11 ` Colin Leroy
2004-12-01 9:22 ` Benjamin Herrenschmidt [this message]
2004-12-01 13:09 ` Colin Leroy
2004-12-01 17:46 ` David Woodhouse
2004-12-02 0:55 ` Timo Reimerdes
2004-12-02 11:08 ` Colin Leroy
2004-12-02 11:24 ` Benjamin Herrenschmidt
2004-12-03 16:41 ` Kjetil Ørbekk
2004-12-03 17:06 ` Federico Gamio
-- strict thread matches above, loose matches on Subject: below --
2004-12-05 10:25 Benjamin Herrenschmidt
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=1101892923.5593.17.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=colin@colino.net \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).