From: Peter Zijlstra <peterz@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Venkatesh Pallipadi <venki@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Suresh Siddha <suresh.b.siddha@intel.com>,
Aaron Durbin <adurbin@google.com>, Paul Turner <pjt@google.com>,
Yong Zhang <yong.zhang0@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Extend mwait idle to optimize away CAL and RES interrupts to an idle CPU -v1
Date: Thu, 23 Feb 2012 10:08:55 +0100 [thread overview]
Message-ID: <1329988135.24994.43.camel@twins> (raw)
In-Reply-To: <20120223075027.GB15306@elte.hu>
On Thu, 2012-02-23 at 08:50 +0100, Ingo Molnar wrote:
> * Venkatesh Pallipadi <venki@google.com> wrote:
> > * We can also eliminate TS_POLLING flag in favor of this. But, that will have
> > a lot more touchpoints and better done as a standlone change.
>
> Should most definitely be done for this series to be acceptble -
> as a preparatory patch in the series, with the feature at the
> end of the series.
I don't think you can, TS_POLLING still works for idle=poll, whereas
this new stuff requires monitor/mwait.
next prev parent reply other threads:[~2012-02-23 9:09 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 0:36 [PATCH] Extend mwait idle to optimize away CAL and RES interrupts to an idle CPU -v1 Venkatesh Pallipadi
2012-02-23 7:50 ` Ingo Molnar
2012-02-23 9:08 ` Peter Zijlstra [this message]
2012-02-23 20:04 ` Venki Pallipadi
2012-02-23 20:03 ` Venki Pallipadi
2012-03-02 0:33 ` Venki Pallipadi
2012-03-02 1:28 ` Suresh Siddha
2012-03-02 1:35 ` Venki Pallipadi
2012-03-02 1:37 ` Suresh Siddha
2012-03-02 2:00 ` Venki Pallipadi
2012-03-02 7:21 ` Ingo Molnar
2012-03-02 17:41 ` Suresh Siddha
2012-03-06 21:41 ` fork_idle from wq cleanup Venkatesh Pallipadi
2012-03-06 21:41 ` [PATCH 1/5] x86: Move fork_idle from wq and idle caching to common code Venkatesh Pallipadi
2012-03-06 21:41 ` [PATCH 2/5] ia64: Use common fork_idle_from_wq in smpboot Venkatesh Pallipadi
2012-03-06 21:41 ` [PATCH 3/5] mips: " Venkatesh Pallipadi
2012-03-06 22:51 ` Ralf Baechle
2012-03-06 21:41 ` [PATCH 4/5] powerpc: " Venkatesh Pallipadi
2012-03-06 21:41 ` [PATCH 5/5] s390: " Venkatesh Pallipadi
2012-03-07 7:00 ` Heiko Carstens
2012-03-07 6:06 ` fork_idle from wq cleanup Suresh Siddha
2012-02-23 9:30 ` [PATCH] Extend mwait idle to optimize away CAL and RES interrupts to an idle CPU -v1 Peter Zijlstra
2012-02-23 19:34 ` Venki Pallipadi
2012-02-24 5:41 ` Yong Zhang
2012-02-24 6:13 ` Yong Zhang
2012-02-27 8:38 ` Peter Zijlstra
2012-02-27 9:08 ` Yong Zhang
2012-02-27 9:30 ` Peter Zijlstra
2012-02-27 9:51 ` Yong Zhang
2012-02-26 1:32 ` Paul E. McKenney
2012-02-27 9:06 ` Yong Zhang
2012-02-27 17:05 ` Paul E. McKenney
2012-02-28 7:12 ` Yong Zhang
2012-02-28 13:05 ` Paul E. McKenney
2012-02-29 6:36 ` Yong Zhang
2012-02-27 8:45 ` Peter Zijlstra
2012-02-27 18:17 ` Venki Pallipadi
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=1329988135.24994.43.camel@twins \
--to=peterz@infradead.org \
--cc=adurbin@google.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=pjt@google.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=venki@google.com \
--cc=yong.zhang0@gmail.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).