qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Benoît Canet" <benoit.canet@irqsave.net>
To: cpufreq@vger.kernel.org, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, gleb@redhat.com,
	viresh.kumar@linaro.org, agraf@suse.de, rjw@sisk.pl,
	pbonzini@redhat.com
Subject: [Qemu-devel] cpufreq and QEMU guests
Date: Mon, 16 Sep 2013 14:15:46 +0200	[thread overview]
Message-ID: <20130916121545.GH5105@irqsave.net> (raw)


Hello,

I know a cloud provider worried about the fact that the /proc/cpuinfo of his
guests give a bogus frequency to his customer.

QEMU and the guests kernel currently have no way to reflect the host frequency
changes to the guests.

The customer compute intensive application then read this information and take
wrong decisions.

I looked at the various Linux cpufreq drivers and they all seems to be table
based. Is it true ?

For example the acpi cpufreq driver have 16 differents pstates at hand to lookup
in the pstate table and get the frequency.

Given that guests can migrate from one hardware to a slightly different hardware
the table may become wrong after live migration.

What would be the best hardware to emulate in order to pass an arbitrary
frequency to the guest ?

Would a pvfreq paravirtualized QEMU hardware and a guest driver implementing
only the callbacks needed to read the frequency be a good idea ?

Best regards

Benoît

ps:
I CC this mail to the other QEMU arch maintainers because the problem must be
the same everywhere where KVM run.

             reply	other threads:[~2013-09-16 12:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-16 12:15 Benoît Canet [this message]
2013-09-16 14:39 ` [Qemu-devel] cpufreq and QEMU guests Alexander Graf
2013-09-16 15:05   ` Benoît Canet
2013-09-16 15:32     ` Gleb Natapov
2013-09-16 15:46       ` Benoît Canet
2013-09-16 15:58         ` Gleb Natapov
2013-09-16 18:42           ` Benoît Canet
2013-09-17  8:58             ` Gleb Natapov

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=20130916121545.GH5105@irqsave.net \
    --to=benoit.canet@irqsave.net \
    --cc=agraf@suse.de \
    --cc=cpufreq@vger.kernel.org \
    --cc=gleb@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rjw@sisk.pl \
    --cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).