[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6071310f-dd4b-6a6d-5578-7b6f72a9b1be@redhat.com>
Date: Thu, 5 Mar 2020 17:42:59 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: Sean Christopherson <sean.j.christopherson@...el.com>
Cc: Vitaly Kuznetsov <vkuznets@...hat.com>,
Wanpeng Li <wanpengli@...cent.com>,
Jim Mattson <jmattson@...gle.com>,
Joerg Roedel <joro@...tes.org>, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, Pu Wen <puwen@...on.cn>
Subject: Re: [PATCH v2 0/7] KVM: x86: CPUID emulation and tracing fixes
On 05/03/20 02:34, Sean Christopherson wrote:
>
> In theory, everything up to the refactoring is non-controversial, i.e. we
> can bikeshed the refactoring without delaying the bug fixes.
Even the refactoring itself is much less controversial. I queued
everything, there's always time to unqueue.
Paolo
> v2:
> - Use Jan's patch to fix the trace bug. [Everyone]
> - Rework Hypervisor/Centaur handling so that only the Hypervisor
> sub-ranges get the restrictive 0xffffff00 mask, and so that Centaur's
> range only gets recognized when the guest vendor is Centaur. [Jim]
> - Add the aforementioned bug fixes.
> - Add a patch to do build time assertions on the vendor string, which
> are hand coded u32s in the emulator (for direct comparison against
> CPUID register output).
> - Drop the patch to add CPUID.maxphyaddr emulator helper. [Paolo]
> - Redo refactoring patches to land them after all the bug fixes
> and to do the refactoring without any semantic changes in the
> emulator.
Powered by blists - more mailing lists