From: Venki Pallipadi <venkatesh.pallipadi@intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>
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: Wed, 19 Dec 2007 12:23:36 -0800 [thread overview]
Message-ID: <20071219202335.GB13605@linux-os.sc.intel.com> (raw)
In-Reply-To: <4769757E.306@zytor.com>
On Wed, Dec 19, 2007 at 11:48:14AM -0800, H. Peter Anvin wrote:
> Ingo Molnar wrote:
> >
> >i dont think it's required for C3 to even turn off any portion of the
> >CPU - if an interrupt arrives after the C3 sequence is initiated but
> >just before dirty cachelines have been flushed then the CPU can just
> >return without touching anything (such as the TLB) - right? So i dont
> >think there's any implicit guarantee of TLB flushing (nor should there
> >be), but in practice, a good C3 sequence would (statistically) turn off
> >large portions of the CPU and hence the TLB as well.
> >
>
> 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.)
>
> Otherwise, what you say here of course is absolutely correct.
>
C3 does not guarantee all cache contents. Infact, atleast on Intel,
L1 will be almost always flushed. Newer more power efficient CPUs does dynamic
cache sizing [1]
C3 just guarantees that the caches are coherent. That is, if they are intact,
then DMA will keep cache consistent.
Thanks,
Venki
[1] - http://download.intel.com/products/processor/core2duo/mobile_prod_brief.pdf
next prev parent reply other threads:[~2007-12-19 20:24 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 [this message]
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
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=20071219202335.GB13605@linux-os.sc.intel.com \
--to=venkatesh.pallipadi@intel.com \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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).