linux-kernel - Re: [PATCH] KVM: VMX: CPU frequency scaling for intel x86

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <7a030232a8002a31520e1c435034f2c9b2f8a858.camel@infradead.org>
Date:   Wed, 01 Jun 2022 13:55:07 +0100
From:   David Woodhouse <dwmw2@...radead.org>
To:     Paolo Bonzini <pbonzini@...hat.com>,
        Metin Kaya <metikaya@...zon.co.uk>, jalliste@...zon.com
Cc:     bp@...en8.de, diapop@...zon.co.uk, hpa@...or.com,
        jmattson@...gle.com, joro@...tes.org, kvm@...r.kernel.org,
        linux-kernel@...r.kernel.org, mingo@...hat.com, rkrcmar@...hat.com,
        sean.j.christopherson@...el.com, tglx@...utronix.de,
        vkuznets@...hat.com, wanpengli@...cent.com, x86@...nel.org
Subject: Re: [PATCH] KVM: VMX: CPU frequency scaling for intel x86_64 KVM
 guests

On Tue, 2022-05-31 at 20:11 +0200, Paolo Bonzini wrote:
> On 5/31/22 13:43, Metin Kaya wrote:
> > Thanks, Jack.
> > 
> > Reviewed-by: Metin Kaya <metikaya@...zon.co.uk>
> > 
> 
> Please try a bit harder.  "Reviewed-by" is neither "this matches what's 
> been forever in the Amazon kernel" 

Oh, it hasn't made it to the Amazon kernel yet. I have started
threatening to *eat* people who even submit stuff to the internal
kernel for review without first posting it upstream.

That does mean you get to see it sooner, which is a mixed blessing :)

> - does not even *apply* to the upstream kernel, because it uses 
> (presumably Amazon-specific) CAP numbers above 10000
> 
> - does not work if the vCPU is moved from one physical CPU to another
> 
> - does not work if the intel_pstate driver writes to MSR_HWP_REQUEST
> 
> - does not include documentation for the new capability
> 
> - does not include a selftest
> 
> - is unacceptable anyway because, as mentioned in the cover letter, it 
> isn't undone when the process exits

That's a useful summary; thank you. I think we should definitely focus
on integrating with cpufreq too.

Is this even a KVM thing?

I don't think we really want to do the change on every vmexit/enter. We
could *maybe* make a case for doing it on entry and then removing the
limit when either returning to *userspace* or scheduling?

But I think even that probably isn't needed. Just let the VMM run at
the same frequency too, as a per-process setting.

> Jack, please understand that I am not really blaming you in any way, and 
> ask some of your colleagues with upstream kernel experience (Alex Graf, 
> David Woodhouse, Filippo Sironi, Jan Schoenherr, Amit Shah are the ones 
> I know) which patches could be good targets for including upstream.

Indeed. As a straw man there are worse ways to start the discussion.
Thanks, Jack.



Download attachment "smime.p7s" of type "application/pkcs7-signature" (5965 bytes)