From: Peter Zijlstra <peterz@infradead.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Jack Allister <jalliste@amazon.com>,
Borislav Petkov <bp@alien8.de>,
diapop@amazon.co.uk, "Anvin, H. Peter" <hpa@zytor.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
kvm <kvm@vger.kernel.org>,
"Kernel Mailing List, Linux" <linux-kernel@vger.kernel.org>,
Metin Kaya <metikaya@amazon.co.uk>,
Ingo Molnar <mingo@redhat.com>, Radim Krcmar <rkrcmar@redhat.com>,
Sean Christopherson <sean.j.christopherson@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: ...\n
Date: Tue, 31 May 2022 17:27:54 +0200 [thread overview]
Message-ID: <YpYz+ltAHRsF5s0u@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CABgObfYYUNb_pEVA2xdUm_U39Wc1=AahJKDx2=9P+aK5=z202w@mail.gmail.com>
On Tue, May 31, 2022 at 04:52:56PM +0200, Paolo Bonzini wrote:
> On Tue, May 31, 2022 at 4:45 PM Peter Zijlstra <peterz@infradead.org> wrote:
> > On Tue, May 31, 2022 at 02:02:36PM +0000, Jack Allister wrote:
> > > The reasoning behind this is that you may want to run a guest at a
> > > lower CPU frequency for the purposes of trying to match performance
> > > parity between a host of an older CPU type to a newer faster one.
> >
> > That's quite ludicrus. Also, then it should be the host enforcing the
> > cpufreq, not the guest.
>
> It is a weird usecase indeed, but actually it *is* enforced by the
> host in Jack's patch.
Clearly I don't understand KVM much; I was thikning that since it was
mucking the with vmx code it was some guest interface.
If it is host control, then it's even more insane, since the host has
plenty existing interfaces for cpufreq control. No need to add more
crazy hacks like this.
next prev parent reply other threads:[~2022-05-31 15:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 10:59 [PATCH] KVM: VMX: CPU frequency scaling for intel x86_64 KVM guests Jack Allister
2022-05-31 11:43 ` Metin Kaya
2022-05-31 18:11 ` Paolo Bonzini
2022-06-01 12:55 ` David Woodhouse
2022-05-31 13:38 ` Peter Zijlstra
2022-05-31 14:02 ` ...\n Jack Allister
2022-05-31 14:44 ` ...\n Peter Zijlstra
2022-05-31 14:52 ` ...\n Durrant, Paul
2022-05-31 15:51 ` ...\n Paolo Bonzini
2022-06-01 7:57 ` ...\n Vitaly Kuznetsov
2022-06-01 8:59 ` ...\n Paolo Bonzini
2022-06-01 10:19 ` ...\n Peter Zijlstra
2022-06-01 6:52 ` ...\n Peter Zijlstra
2022-06-01 8:03 ` ...\n Vitaly Kuznetsov
2022-06-01 8:25 ` ...\n Christophe de Dinechin
2022-06-01 8:54 ` ...\n Durrant, Paul
2022-06-01 8:57 ` ...\n Paolo Bonzini
2022-06-01 9:20 ` ...\n Durrant, Paul
2022-06-01 9:43 ` ...\n Amit Shah
2022-06-01 13:14 ` ...\n David Woodhouse
2022-05-31 14:52 ` ...\n Paolo Bonzini
2022-05-31 15:27 ` Peter Zijlstra [this message]
2022-05-31 15:01 ` [PATCH] KVM: VMX: CPU frequency scaling for intel x86_64 KVM guests Vitaly Kuznetsov
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=YpYz+ltAHRsF5s0u@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=diapop@amazon.co.uk \
--cc=hpa@zytor.com \
--cc=jalliste@amazon.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=metikaya@amazon.co.uk \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@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
all inboxes | Powered by JetHome®