From: Peter Zijlstra <peterz@infradead.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Marcelo Tosatti" <mtosatti@redhat.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
kvm-devel <kvm@vger.kernel.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Radim KrÄ?máÅ?" <rkrcmar@redhat.com>,
"Andrea Arcangeli" <aarcange@redhat.com>,
"Wanpeng Li" <kernellwp@gmail.com>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
"Raslan KarimAllah" <karahmed@amazon.de>,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
"Ankur Arora" <ankur.a.arora@oracle.com>,
"Christian Borntraeger" <borntraeger@de.ibm.com>,
"Linux PM" <linux-pm@vger.kernel.org>
Subject: Re: [patch 0/3] cpuidle-haltpoll driver (v2)
Date: Mon, 17 Jun 2019 17:57:22 +0200 [thread overview]
Message-ID: <20190617155722.GJ3436@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CAJZ5v0gPbSXB3r71XaT-4Q7LsiFO_UVymBwOmU8J1W5+COk_1g@mail.gmail.com>
On Tue, Jun 11, 2019 at 11:24:39PM +0200, Rafael J. Wysocki wrote:
> > Peter Zijlstra suggested a cpuidle driver for this.
>
> So I wonder what his rationale was.
I was thinking we don't need this hard-coded in the idle loop when virt
can load a special driver.
next prev parent reply other threads:[~2019-06-17 15:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190603225242.289109849@amt.cnet>
2019-06-07 9:49 ` [patch 0/3] cpuidle-haltpoll driver (v2) Rafael J. Wysocki
2019-06-07 17:16 ` Marcelo Tosatti
2019-06-07 18:22 ` Paolo Bonzini
2019-06-07 21:38 ` Marcelo Tosatti
2019-06-10 14:59 ` Marcelo Tosatti
2019-06-10 22:03 ` Rafael J. Wysocki
2019-06-11 14:26 ` Marcelo Tosatti
2019-06-11 21:24 ` Rafael J. Wysocki
2019-06-17 15:57 ` Peter Zijlstra [this message]
[not found] ` <20190603225254.212931277@amt.cnet>
2019-06-07 9:54 ` [patch 1/3] drivers/cpuidle: add cpuidle-haltpoll driver Rafael J. Wysocki
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=20190617155722.GJ3436@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=aarcange@redhat.com \
--cc=ankur.a.arora@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=borntraeger@de.ibm.com \
--cc=karahmed@amazon.de \
--cc=kernellwp@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=rkrcmar@redhat.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).