From: Randy Dunlap <rdunlap@infradead.org>
To: David Dai <davidai@google.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Saravana Kannan <saravanak@google.com>
Cc: Quentin Perret <qperret@google.com>,
Masami Hiramatsu <mhiramat@google.com>,
Will Deacon <will@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Marc Zyngier <maz@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Pavan Kondeti <quic_pkondeti@quicinc.com>,
Gupta Pankaj <pankaj.gupta@amd.com>, Mel Gorman <mgorman@suse.de>,
kernel-team@android.com, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] cpufreq: add virtual-cpufreq driver
Date: Mon, 31 Jul 2023 15:02:47 -0700 [thread overview]
Message-ID: <afac2810-f93e-eda5-975e-041ac4b908b5@infradead.org> (raw)
In-Reply-To: <20230731174613.4133167-3-davidai@google.com>
On 7/31/23 10:46, David Dai wrote:
> diff --git a/drivers/cpufreq/Kconfig b/drivers/cpufreq/Kconfig
> index f429b9b37b76..3977ca796747 100644
> --- a/drivers/cpufreq/Kconfig
> +++ b/drivers/cpufreq/Kconfig
> @@ -217,6 +217,21 @@ config CPUFREQ_DT
>
> If in doubt, say N.
>
> +config CPUFREQ_VIRT
> + tristate "Virtual cpufreq driver"
> + depends on OF
> + select PM_OPP
> + help
The 4 lines above should be indented with one tab (not 8 spaces).
> + This adds a virtualized cpufreq driver for guest kernels that
> + read/writes to a MMIO region for a virtualized cpufreq device to
reads/writes to an MMIO region
> + communicate with the host. It sends frequency updates to the host
> + which gets used as a hint to schedule vCPU threads and select CPU
> + frequency. If a VM does not support a virtualized FIE such as AMUs,
> + it updates the frequency scaling factor by polling host CPU frequency
> + to enable accurate Per-Entity Load Tracking for tasks running in the guest.
> +
> + If in doubt, say N.
--
~Randy
next prev parent reply other threads:[~2023-07-31 22:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 17:46 [PATCH v3 0/2] Improve VM CPUfreq and task placement behavior David Dai
2023-07-31 17:46 ` [PATCH v3 1/2] dt-bindings: cpufreq: add bindings for virtual cpufreq David Dai
2023-07-31 18:12 ` Rob Herring
2023-08-05 19:38 ` Krzysztof Kozlowski
2023-08-08 23:31 ` Saravana Kannan
2023-08-09 6:28 ` Krzysztof Kozlowski
2023-07-31 17:46 ` [PATCH v3 2/2] cpufreq: add virtual-cpufreq driver David Dai
2023-07-31 22:02 ` Randy Dunlap [this message]
2023-07-31 23:46 ` David Dai
2023-08-01 9:36 ` Viresh Kumar
2023-08-02 22:16 ` Saravana Kannan
2023-08-03 5:51 ` Viresh Kumar
2023-08-04 22:24 ` Saravana Kannan
2023-08-03 16:50 ` David Dai
2023-08-04 4:42 ` Viresh Kumar
2023-08-01 9:45 ` Quentin Perret
2023-08-01 9:49 ` Quentin Perret
2023-08-04 22:23 ` Saravana Kannan
2023-08-03 4:18 ` Pavan Kondeti
2023-08-04 23:46 ` David Dai
2023-08-07 3:22 ` Pavan Kondeti
2023-08-24 23:55 ` David Dai
2023-08-12 2:55 ` kernel test robot
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=afac2810-f93e-eda5-975e-041ac4b908b5@infradead.org \
--to=rdunlap@infradead.org \
--cc=conor+dt@kernel.org \
--cc=davidai@google.com \
--cc=devicetree@vger.kernel.org \
--cc=dietmar.eggemann@arm.com \
--cc=kernel-team@android.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=maz@kernel.org \
--cc=mgorman@suse.de \
--cc=mhiramat@google.com \
--cc=oliver.upton@linux.dev \
--cc=pankaj.gupta@amd.com \
--cc=peterz@infradead.org \
--cc=qperret@google.com \
--cc=quic_pkondeti@quicinc.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=saravanak@google.com \
--cc=sudeep.holla@arm.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).