On 16/06/2023 2:10 pm, Roger Pau Monne wrote: > Introduce a local xc_cpu_policy_t and use it to simplify some of the > logic in the function: > > * Populate the introduced xc_cpu_policy_t with the current domain > policy, which will already be the default for the given domain > type. This avoids fetching and processing any default policy.
I'm afraid this isn't accurate. Right now, xc_cpuid_apply_policy() is idempotent on a domain, but after this change, it's only true for the first call after domain creation. I can't remember if we depend on this behaviour right now, but my gut feeling is that it's going to become more important as we gain more opt-in features. ~Andrew
