From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Anthony Harivel <aharivel@redhat.com>, kvm@vger.kernel.org
Cc: rjarry@redhat.com, Paolo Bonzini <pbonzini@redhat.com>,
Christophe Fontaine <cfontain@redhat.com>
Subject: Re: [RFC] KVM: x86: Give host userspace control for MSR_RAPL_POWER_UNIT and MSR_PKG_POWER_STATUS
Date: Thu, 19 Jan 2023 13:57:40 +0800 [thread overview]
Message-ID: <d635edea-e181-3498-ceff-72434ab856cf@intel.com> (raw)
In-Reply-To: <20230118142123.461247-1-aharivel@redhat.com>
On 1/18/2023 10:21 PM, Anthony Harivel wrote:
> Allow userspace to update the MSR_RAPL_POWER_UNIT and
> MSR_PKG_POWER_STATUS powercap registers. By default, these MSRs still
> return 0.
>
> This enables VMMs running on top of KVM with access to energy metrics
> like /sys/devices/virtual/powercap/*/*/energy_uj to compute VMs power
> values in proportion with other metrics (e.g. CPU %guest, steal time,
> etc.) and periodically update the MSRs with ioctl KVM_SET_MSRS so that
> the guest OS can consume them using power metering tools.
>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Christophe Fontaine <cfontain@redhat.com>
> Signed-off-by: Anthony Harivel <aharivel@redhat.com>
> ---
>
> Notes:
> The main goal of this patch is to bring a first step to give energy
> awareness to VMs.
>
> As of today, KVM always report 0 in these MSRs since the entire host
> power consumption needs to be hidden from the guests. However, there is
> no fallback mechanism for VMs to measure their power usage.
>
> The idea is to let the VMMs running on top of KVM periodically update
> those MSRs with representative values of the VM's power consumption.
>
> If this solution is accepted, VMMs like QEMU will need to be patched to
> set proper values in these registers and enable power metering in
> guests.
>
> I am submitting this as an RFC to get input/feedback from a broader
> audience who may be aware of potential side effects of such a mechanism.
Set aside how user space VMM emulate these 2 MSRs correctly, it can
request the MSR READ to exit to user space via KVM_X86_SET_MSR_FILTER.
So user space VMM can just enable the read filter of these 2 MSRs and
provide the emulation itself.
next prev parent reply other threads:[~2023-01-19 5:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 14:21 [RFC] KVM: x86: Give host userspace control for MSR_RAPL_POWER_UNIT and MSR_PKG_POWER_STATUS Anthony Harivel
2023-01-19 5:57 ` Xiaoyao Li [this message]
2023-01-20 8:59 ` Anthony Harivel
2023-01-19 23:27 ` Paolo Bonzini
2023-01-20 16:47 ` Anthony Harivel
2023-01-20 16:57 ` Paolo Bonzini
2023-01-23 12:43 ` Anthony Harivel
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=d635edea-e181-3498-ceff-72434ab856cf@intel.com \
--to=xiaoyao.li@intel.com \
--cc=aharivel@redhat.com \
--cc=cfontain@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rjarry@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