From: Jack Allister <jalliste@amazon.com>
To: <peterz@infradead.org>
Cc: <bp@alien8.de>, <diapop@amazon.co.uk>, <hpa@zytor.com>,
<jalliste@amazon.com>, <jmattson@google.com>, <joro@8bytes.org>,
<kvm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<metikaya@amazon.co.uk>, <mingo@redhat.com>,
<pbonzini@redhat.com>, <rkrcmar@redhat.com>,
<sean.j.christopherson@intel.com>, <tglx@linutronix.de>,
<vkuznets@redhat.com>, <wanpengli@tencent.com>, <x86@kernel.org>
Subject: ...\n
Date: Tue, 31 May 2022 14:02:36 +0000 [thread overview]
Message-ID: <20220531140236.1435-1-jalliste@amazon.com> (raw)
In-Reply-To: <YpYaYK7a28DFT5Ne@hirez.programming.kicks-ass.net>
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.
next prev parent reply other threads:[~2022-05-31 14:10 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 ` Jack Allister [this message]
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 ` ...\n Peter Zijlstra
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=20220531140236.1435-1-jalliste@amazon.com \
--to=jalliste@amazon.com \
--cc=bp@alien8.de \
--cc=diapop@amazon.co.uk \
--cc=hpa@zytor.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=peterz@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).