[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] x86/ACPI: _PDC bits vs HWP/CPPC


  • To: Roger Pau Monné <roger.pau@xxxxxxxxxx>
  • From: Jan Beulich <jbeulich@xxxxxxxx>
  • Date: Thu, 5 Mar 2026 12:39:51 +0100
  • Autocrypt: addr=jbeulich@xxxxxxxx; keydata= xsDiBFk3nEQRBADAEaSw6zC/EJkiwGPXbWtPxl2xCdSoeepS07jW8UgcHNurfHvUzogEq5xk hu507c3BarVjyWCJOylMNR98Yd8VqD9UfmX0Hb8/BrA+Hl6/DB/eqGptrf4BSRwcZQM32aZK 7Pj2XbGWIUrZrd70x1eAP9QE3P79Y2oLrsCgbZJfEwCgvz9JjGmQqQkRiTVzlZVCJYcyGGsD /0tbFCzD2h20ahe8rC1gbb3K3qk+LpBtvjBu1RY9drYk0NymiGbJWZgab6t1jM7sk2vuf0Py O9Hf9XBmK0uE9IgMaiCpc32XV9oASz6UJebwkX+zF2jG5I1BfnO9g7KlotcA/v5ClMjgo6Gl MDY4HxoSRu3i1cqqSDtVlt+AOVBJBACrZcnHAUSuCXBPy0jOlBhxPqRWv6ND4c9PH1xjQ3NP nxJuMBS8rnNg22uyfAgmBKNLpLgAGVRMZGaGoJObGf72s6TeIqKJo/LtggAS9qAUiuKVnygo 3wjfkS9A3DRO+SpU7JqWdsveeIQyeyEJ/8PTowmSQLakF+3fote9ybzd880fSmFuIEJldWxp Y2ggPGpiZXVsaWNoQHN1c2UuY29tPsJgBBMRAgAgBQJZN5xEAhsDBgsJCAcDAgQVAggDBBYC AwECHgECF4AACgkQoDSui/t3IH4J+wCfQ5jHdEjCRHj23O/5ttg9r9OIruwAn3103WUITZee e7Sbg12UgcQ5lv7SzsFNBFk3nEQQCACCuTjCjFOUdi5Nm244F+78kLghRcin/awv+IrTcIWF hUpSs1Y91iQQ7KItirz5uwCPlwejSJDQJLIS+QtJHaXDXeV6NI0Uef1hP20+y8qydDiVkv6l IreXjTb7DvksRgJNvCkWtYnlS3mYvQ9NzS9PhyALWbXnH6sIJd2O9lKS1Mrfq+y0IXCP10eS FFGg+Av3IQeFatkJAyju0PPthyTqxSI4lZYuJVPknzgaeuJv/2NccrPvmeDg6Coe7ZIeQ8Yj t0ARxu2xytAkkLCel1Lz1WLmwLstV30g80nkgZf/wr+/BXJW/oIvRlonUkxv+IbBM3dX2OV8 AmRv1ySWPTP7AAMFB/9PQK/VtlNUJvg8GXj9ootzrteGfVZVVT4XBJkfwBcpC/XcPzldjv+3 HYudvpdNK3lLujXeA5fLOH+Z/G9WBc5pFVSMocI71I8bT8lIAzreg0WvkWg5V2WZsUMlnDL9 mpwIGFhlbM3gfDMs7MPMu8YQRFVdUvtSpaAs8OFfGQ0ia3LGZcjA6Ik2+xcqscEJzNH+qh8V m5jjp28yZgaqTaRbg3M/+MTbMpicpZuqF4rnB0AQD12/3BNWDR6bmh+EkYSMcEIpQmBM51qM EKYTQGybRCjpnKHGOxG0rfFY1085mBDZCH5Kx0cl0HVJuQKC+dV2ZY5AqjcKwAxpE75MLFkr wkkEGBECAAkFAlk3nEQCGwwACgkQoDSui/t3IH7nnwCfcJWUDUFKdCsBH/E5d+0ZnMQi+G0A nAuWpQkjM1ASeQwSHEeAWPgskBQL
  • Cc: "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Jason Andryuk <jason.andryuk@xxxxxxx>, Penny Zheng <Penny.Zheng@xxxxxxx>
  • Delivery-date: Thu, 05 Mar 2026 11:39:58 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 05.03.2026 11:17, Roger Pau Monné wrote:
> On Thu, Mar 05, 2026 at 10:20:02AM +0100, Jan Beulich wrote:
>> On 05.03.2026 09:50, Roger Pau Monné wrote:
>>> Since we have the parsing of the ACPI related data done from dom0 it's
>>> not only Xen that needs to support the feature, but dom0 also needs to
>>> know how to parse it.  Or we just assume the driver in dom0 must
>>> strictly know how to parse data from the features enabled by Xen.
>>>
>>> Maybe Xen supported bits should be & with the dom0 ones?  So dom0
>>> would set what it can parse, and Xen would AND that with what the
>>> cpufreq drivers support?  However that would be an ABI change.
>>
>> What cpufreq drivers are you talking about here?
> 
> I was talking about the Xen cpufreq driver, sorry the context was
> confusing.
> 
>> When Xen handles P-
>> state transitions, the drivers in Dom0 would preferably not even be
>> loaded. That's what the forward-port did. Upstream they may be loaded,
>> but they then can't actually do anything (and they may exit early).
> 
> Well, yes, on FreeBSD I simply overtake the native ACPI Processor
> driver with a Xen specific one that has higher priority.  So the
> native ACPI Processor driver doesn't even attach.  I think Linux is
> slightly different in that it allows the native driver to do the
> fetching of the information, and then the Xen driver only does the
> uploading.
> 
>> Coordination is necessary only with the ACPI driver(s), and that's what
>> this function is about.
> 
> I think Xen also needs coordination with the driver in dom0 that
> fetches the information from ACPI?

That's what I meant with "ACPI driver(s)".

>  It's not only Xen that needs to
> report what the cpufreq driver support, but also dom0 would need to
> expose what it can correctly parse.

Hmm, yes, strictly speaking we should tie setting of respective bits to
Dom0 having uploaded corresponding data. The order of these operations
may, however, be at best undefined (and possibly be well defined in the
unhelpful - for us - order). I don't think I see anything we can do
about this.

Jan



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.