From: Daniel Lezcano <daniel.lezcano@free.fr>
To: kvm@vger.kernel.org
Subject: question regarding intel_idle inside kvm
Date: Thu, 15 Mar 2012 23:19:49 +0100 [thread overview]
Message-ID: <4F626B05.9070909@free.fr> (raw)
Hi all,
I recently did some modification in the cpuidle core and the patches
were merge to linux-next.
Someone reported a problem with the intel_idle cpuidle driver.
I tried to reproduce the problem with kvm but the kernel fails to
intialize the driver because of intel_intel_init function fails in the
processor probe.
After digging a bit, I found it fails at:
drivers/idle/intel_idle.c
static int intel_idle_probe(void)
{
...
if (boot_cpu_data.cpuid_level < CPUID_MWAIT_LEAF)
return -ENODEV;
^^^^^
...
}
I assumed the virtualized processor does not support this, so I
specified the "-cpu host" because the host was running the intel_idle
driver. But the driver still fails in kvm.
I was wondering why that happens ? Does anyone have an idea of this
problem ?
Thanks in advance
-- Daniel
next reply other threads:[~2012-03-15 22:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 22:19 Daniel Lezcano [this message]
2012-03-19 12:31 ` question regarding intel_idle inside kvm Avi Kivity
2012-03-19 13:20 ` Daniel Lezcano
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=4F626B05.9070909@free.fr \
--to=daniel.lezcano@free.fr \
--cc=kvm@vger.kernel.org \
/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