All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Sommrey <jo@sommrey.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	tony@atomide.com, len.brown@intel.com, erik@slagter.name,
	alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH] amd76x_pm: C3 powersaving for AMD K7
Date: Fri, 3 Feb 2006 08:03:30 +0100	[thread overview]
Message-ID: <20060203070329.GA5414@sommrey.de> (raw)
In-Reply-To: <20060202143725.46d218dc.akpm@osdl.org>

On Thu, Feb 02, 2006 at 02:37:25PM -0800, Andrew Morton wrote:
> Joerg Sommrey <jo@sommrey.de> wrote:
> >
> > This is a processor idle module for AMD SMP 760MP(X) based systems.
> >
> 
> Len's comments about loss of cache coherency on some machines possibly
> causing corruption made me drop this patch.   Was I wrong to do so?
> 
You maintain -mm, so it's your decision.  I don't think it is a question
of right or wrong.  If you regard this stuff as too risky, dropping
it is ok.

However, I disagree with Len in two points:
- I cannot see a problem witch cache snooping.  The AMD-768 docs clearly
  states that trying to snoop the cache while in C3 is a resume event.
- Enabling C2/C3 in the BIOS would be a very bad thing IMHO.  From all
  the testing with amd76x_pm I found that is very tricky to go into
  C2/C3 "the right way".  Simply reading the PM register without a
  suitable logic around leads to all kinds of instabilities.  You need
  to implement this logic and then enable the hardware.  The BIOS cannot
  do this.

-jo

-- 
-rw-r--r--  1 jo users 63 2006-02-03 07:43 /home/jo/.signature

  reply	other threads:[~2006-02-03  7:04 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-02 22:24 [PATCH] amd76x_pm: C3 powersaving for AMD K7 Joerg Sommrey
2006-02-02 22:37 ` Andrew Morton
2006-02-03  7:03   ` Joerg Sommrey [this message]
2006-02-02 22:43 ` Dave Jones
  -- strict thread matches above, loose matches on Subject: below --
2006-02-03 18:40 Brown, Len
2006-02-04 10:31 ` Erik Slagter
2006-02-04 10:49   ` Pavel Troller
2006-02-03 18:28 Brown, Len
2006-02-03 18:28 ` Brown, Len
2006-02-03 18:20 Brown, Len
2006-02-03  8:45 Brown, Len
2006-02-03  8:45 ` Brown, Len
2006-02-03  9:35 ` Erik Slagter
2006-02-03 10:31   ` Pavel Troller
2006-02-03 14:16 ` Joerg Sommrey
2006-02-03 15:59 ` Juhani Rautiainen
2006-02-03 17:02   ` Erik Slagter
2006-02-08 20:10   ` Pavel Machek
2006-02-02  1:35 Brown, Len
2006-02-02  1:35 ` Brown, Len
2006-02-02  1:50 ` Alan Cox
2006-02-02  9:50   ` Erik Slagter
2006-02-02 19:38     ` Tony Lindgren
2006-02-03  9:21 ` Erik Slagter
2006-02-03  9:33   ` Pavel Troller
2006-02-03  9:39     ` Erik Slagter
2006-02-03 10:14       ` Pavel Troller
2006-02-03 10:28         ` Erik Slagter
2006-02-01 18:11 Brown, Len
2006-02-01 18:11 ` Brown, Len
2006-02-01 18:18 ` Erik Slagter
2006-02-01 18:40   ` Tony Lindgren
2006-02-01 19:13 ` Joerg Sommrey
2006-01-31 18:55 Joerg Sommrey
2006-02-01  3:34 ` Andrew Morton
2006-02-01 10:25   ` Erik Slagter
2006-02-01 17:20   ` Tony Lindgren

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=20060203070329.GA5414@sommrey.de \
    --to=jo@sommrey.de \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=erik@slagter.name \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony@atomide.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.