linux-kernel - RE: ...\n

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: <b0a029b784fe4648b1351042fdca6e11@EX13D32EUC003.ant.amazon.com>
Date:   Wed, 1 Jun 2022 09:20:58 +0000
From:   "Durrant, Paul" <pdurrant@...zon.co.uk>
To:     Paolo Bonzini <pbonzini@...hat.com>,
        Vitaly Kuznetsov <vkuznets@...hat.com>,
        Peter Zijlstra <peterz@...radead.org>
CC:     "Allister, Jack" <jalliste@...zon.com>,
        "bp@...en8.de" <bp@...en8.de>,
        "diapop@...zon.co.uk" <diapop@...zon.co.uk>,
        "hpa@...or.com" <hpa@...or.com>,
        "jmattson@...gle.com" <jmattson@...gle.com>,
        "joro@...tes.org" <joro@...tes.org>,
        "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "metikaya@...zon.co.uk" <metikaya@...zon.co.uk>,
        "mingo@...hat.com" <mingo@...hat.com>,
        "rkrcmar@...hat.com" <rkrcmar@...hat.com>,
        "sean.j.christopherson@...el.com" <sean.j.christopherson@...el.com>,
        "tglx@...utronix.de" <tglx@...utronix.de>,
        "wanpengli@...cent.com" <wanpengli@...cent.com>,
        "x86@...nel.org" <x86@...nel.org>
Subject: RE: ...\n

> -----Original Message-----
> From: Paolo Bonzini <pbonzini@...hat.com>
> Sent: 01 June 2022 09:57
> To: Durrant, Paul <pdurrant@...zon.co.uk>; Vitaly Kuznetsov <vkuznets@...hat.com>; Peter Zijlstra
> <peterz@...radead.org>
> Cc: Allister, Jack <jalliste@...zon.com>; 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;
> metikaya@...zon.co.uk; mingo@...hat.com; rkrcmar@...hat.com; sean.j.christopherson@...el.com;
> tglx@...utronix.de; wanpengli@...cent.com; x86@...nel.org
> Subject: RE: [EXTERNAL]...\n
> 
> CAUTION: This email originated from outside of the organization. Do not click links or open
> attachments unless you can confirm the sender and know the content is safe.
> 
> 
> 
> On 6/1/22 10:54, Durrant, Paul wrote:
> > That is exactly the case. This is not 'some hare-brained money
> > scheme'; there is genuine concern that moving a VM from old h/w to
> > new h/w may cause it to run 'too fast', breaking any such calibration
> > done by the guest OS/application. I also don't have any real-world
> > examples, but bugs may well be reported and having a lever to address
> > them is IMO a good idea. However, I also agree with Paolo that KVM
> > doesn't really need to be doing this when the VMM could do the job
> > using cpufreq, so we'll pursue that option instead. (FWIW the reason
> > for involving KVM was to do the freq adjustment right before entering
> > the guest and then remove the cap right after VMEXIT).
> 
> But if so, you still would submit the full feature, wouldn't you?
> 

Yes; the commit message should have at least said that we'd follow up... but a full series would have been a better idea.

> Paul, thanks for chiming in, and sorry for leaving you out of the list
> of people that can help Jack with his upstreaming efforts.  :)
> 

NP.

  Paul

> Paolo