From: Paolo Bonzini <pbonzini@redhat.com>
To: Metin Kaya <metikaya@amazon.co.uk>, jalliste@amazon.com
Cc: bp@alien8.de, diapop@amazon.co.uk, hpa@zytor.com,
jmattson@google.com, joro@8bytes.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
rkrcmar@redhat.com, sean.j.christopherson@intel.com,
tglx@linutronix.de, vkuznets@redhat.com, wanpengli@tencent.com,
x86@kernel.org
Subject: Re: [PATCH] KVM: VMX: CPU frequency scaling for intel x86_64 KVM guests
Date: Tue, 31 May 2022 20:11:33 +0200 [thread overview]
Message-ID: <0194b22a-38a1-08a1-a576-de6463389ce4@redhat.com> (raw)
In-Reply-To: <20220531114333.29153-1-metikaya@amazon.co.uk>
On 5/31/22 13:43, Metin Kaya wrote:
> Thanks, Jack.
>
> Reviewed-by: Metin Kaya <metikaya@amazon.co.uk>
>
Please try a bit harder. "Reviewed-by" is neither "this matches what's
been forever in the Amazon kernel" nor "I guarantee that Jack is a nice
guy and doesn't screw up". I'm sure he is but everybody screws up, and
in this case the patch:
- 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
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.
Paolo
next prev parent reply other threads:[~2022-05-31 18:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 10:59 Jack Allister
2022-05-31 11:43 ` Metin Kaya
2022-05-31 18:11 ` Paolo Bonzini [this message]
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 ` ...\n Peter Zijlstra
2022-05-31 15:01 ` [PATCH] KVM: VMX: CPU frequency scaling for intel x86_64 KVM guests Vitaly Kuznetsov
2022-05-31 11:16 Jack Allister
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=0194b22a-38a1-08a1-a576-de6463389ce4@redhat.com \
--to=pbonzini@redhat.com \
--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=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®