From: Baorui.Liu <baorliu@amd.com>
To: <linux-pm@vger.kernel.org>
Cc: <rafael@kernel.org>, <viresh.kumar@linaro.org>,
<saravanak@kernel.org>, <mst@redhat.com>, <jasowangio@gmail.com>,
<eperezma@redhat.com>, <xuanzhuo@linux.alibaba.com>,
<virtualization@lists.linux.dev>, Baorui.Liu <baorliu@amd.com>
Subject: [RFC PATCH v2 0/1] cpufreq: virtio frontend to report host CPU frequency
Date: Tue, 22 Sep 2026 17:02:23 +0800 [thread overview]
Message-ID: <20260922090224.430-1-baorliu@amd.com> (raw)
In-Reply-To: <20260916073735.541-1-baorliu@amd.com>
This is RFC v2 of the guest virtio-cpufreq frontend.
Changes since RFC v1
====================
- Fix 0-day kbuild error: cpufreq_generic_attr is gone on current
linux-pm; use cpufreq_freq_attr_scaling_available_freqs.
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202609191437.OaXd0Blz-lkp@intel.com/
RFC notes unchanged: experimental virtio ID 42, hardcoded OPPs,
sleeping .get(), QEMU backend is a separate series.
v1: https://lore.kernel.org/r/20260916073735.541-1-baorliu@amd.com
Baorui.Liu (1):
cpufreq: virtio: add driver to report host frequency to guests
drivers/cpufreq/Kconfig | 14 ++
drivers/cpufreq/Makefile | 1 +
drivers/cpufreq/virtio-cpufreq.c | 240 +++++++++++++++++++++++++++++++
include/uapi/linux/virtio_ids.h | 1 +
4 files changed, 256 insertions(+)
create mode 100644 drivers/cpufreq/virtio-cpufreq.c
--
2.34.1
next prev parent reply other threads:[~2026-09-22 9:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 7:37 [RFC PATCH 0/1] cpufreq: virtio frontend to report host CPU frequency Baorui.Liu
2026-09-16 7:37 ` [RFC PATCH 1/1] cpufreq: virtio: add driver to report host frequency to guests Baorui.Liu
2026-09-22 9:02 ` Baorui.Liu [this message]
2026-09-22 9:22 ` [RFC PATCH v2 0/1] cpufreq: virtio frontend to report host CPU frequency Michael S. Tsirkin
2026-09-22 9:02 ` [RFC PATCH v2 1/1] cpufreq: virtio: add driver to report host frequency to guests Baorui.Liu
2026-09-24 7:18 ` Saravana Kannan
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=20260922090224.430-1-baorliu@amd.com \
--to=baorliu@amd.com \
--cc=eperezma@redhat.com \
--cc=jasowangio@gmail.com \
--cc=linux-pm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=rafael@kernel.org \
--cc=saravanak@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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