linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	Venki Pallipadi <venkatesh.pallipadi@intel.com>,
	Thomas Gleixner <tglx@linutronix.de>, Len Brown <lenb@kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: Voluntary leave_mm before entering ACPI C3
Date: Thu, 20 Dec 2007 10:32:05 -0800	[thread overview]
Message-ID: <476AB525.2050407@zytor.com> (raw)
In-Reply-To: <20071220102202.64f395a7@laptopd505.fenrus.org>

Arjan van de Ven wrote:
> On Thu, 20 Dec 2007 08:16:54 -0800
> "H. Peter Anvin" <hpa@zytor.com> wrote:
> 
>> Arjan van de Ven wrote:
>>> On Wed, 19 Dec 2007 11:48:14 -0800
>>> "H. Peter Anvin" <hpa@zytor.com> wrote:
>>>
>>>> I think C3 guarantees that the cache contents stay intact, and thus
>>>> it might make sense in some technology to preserve the TLB as well
>>>> (being a kind of cache.)
>>> that sounds nice. It's fiction though ;-)
>>>
>>> The thing to realize is that linux only sees "ACPI C3"; the BIOS
>>> maps that C3 to.. well any of the C states the processor in the
>>> system has. What you're saying is afaik correct for the *hardware*
>>> C3, not for the "C3" that Linux sees..
>>>
>> Well, it can only map ACPI C3 to a state which is no more "dead" than 
>> what would normally be permitted by C3.  IIRC, C3 is allowed to
>> require that DMA be turned off (unlike C2), but is not allowed to
>> lose the CPU state.
> 
> state isn't lost if the tlb or the caches are flushed... 
> (properly, eg all pending writebacks are written back first etc)
> 

Oh, right.  My bad.

Of course C3 doesn't guarantee cache retention, only cache coherency.

	-hpa

  reply	other threads:[~2007-12-20 18:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-19 18:34 [PATCH] x86: Voluntary leave_mm before entering ACPI C3 Venki Pallipadi
2007-12-19 19:32 ` Ingo Molnar
2007-12-19 19:36   ` H. Peter Anvin
2007-12-19 19:40     ` Ingo Molnar
2007-12-19 19:48       ` H. Peter Anvin
2007-12-19 20:23         ` Venki Pallipadi
2007-12-20  7:53         ` Arjan van de Ven
2007-12-20 16:16           ` H. Peter Anvin
2007-12-20 18:22             ` Arjan van de Ven
2007-12-20 18:32               ` H. Peter Anvin [this message]
2007-12-20 19:28             ` Len Brown
2007-12-19 19:56       ` Venki Pallipadi
2007-12-19 20:54   ` Ingo Molnar
2007-12-20  2:08   ` Venki Pallipadi
2007-12-20  9:31     ` Ingo Molnar

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=476AB525.2050407@zytor.com \
    --to=hpa@zytor.com \
    --cc=arjan@infradead.org \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=venkatesh.pallipadi@intel.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 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).