From: Thomas Gleixner <tglx@linutronix.de>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jacob Pan <jacob.jun.pan@linux.intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Yang Zhang <yang.zhang.wz@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kvm@vger.kernel.org, Wanpeng Li <wanpeng.li@hotmail.com>,
Paolo Bonzini <pbonzini@redhat.com>,
rkrcmar@redhat.com, dmatlack@google.com, agraf@suse.de,
Peter Zijlstra <peterz@infradead.org>,
Len Brown <lenb@kernel.org>, Linux PM <linux-pm@vger.kernel.org>
Subject: Re: [PATCH RFC hack dont apply] intel_idle: support running within a VM
Date: Wed, 4 Oct 2017 09:56:42 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1710040955450.1878@nanos> (raw)
In-Reply-To: <20171004050939-mutt-send-email-mst@kernel.org>
On Wed, 4 Oct 2017, Michael S. Tsirkin wrote:
> On Tue, Oct 03, 2017 at 11:02:55PM +0200, Thomas Gleixner wrote:
> > There is the series from Audrey which makes use of the various idle
> > prediction mechanisms, scheduler, irq timings, idle governor to get an idea
> > about the estimated idle time. Exactly this information can be fed to the
> > kvmidle driver which can act accordingly.
> >
> > Hacking a random hardware specific idle driver is definitely the wrong
> > approach. It might be useful to chain the kvmidle driver and hardware
> > specific drivers at some point, i.e. if the kvmdriver decides not to exit
> > it delegates the mwait decision to the proper hardware driver in order not
> > to reimplement all the required logic again.
>
> By making changes to idle core to allow that chaining?
> Does this sound like something reasonable?
At least for me it makes sense to avoid code duplication. But thats up to
the cpuidle maintainers to decide at the end.
Thanks,
tglx
next prev parent reply other threads:[~2017-10-04 7:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 22:01 [PATCH RFC hack dont apply] intel_idle: support running within a VM Michael S. Tsirkin
2017-09-29 23:21 ` Rafael J. Wysocki
2017-10-02 17:12 ` Jacob Pan
2017-10-03 21:02 ` Thomas Gleixner
2017-10-04 2:11 ` Michael S. Tsirkin
2017-10-04 7:56 ` Thomas Gleixner [this message]
2017-10-04 20:18 ` Rafael J. Wysocki
2017-10-04 2:09 ` Michael S. Tsirkin
2017-10-04 17:09 ` Jacob Pan
2017-10-04 17:12 ` Michael S. Tsirkin
2017-10-04 18:31 ` Jacob Pan
2017-10-05 10:44 ` Paolo Bonzini
2017-10-06 3:37 ` Michael S. Tsirkin
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=alpine.DEB.2.20.1710040955450.1878@nanos \
--to=tglx@linutronix.de \
--cc=agraf@suse.de \
--cc=dmatlack@google.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rkrcmar@redhat.com \
--cc=wanpeng.li@hotmail.com \
--cc=yang.zhang.wz@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