[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZWYq9W3D8JCAPoc8@google.com>
Date: Tue, 28 Nov 2023 10:01:25 -0800
From: Sean Christopherson <seanjc@...gle.com>
To: Lai Jiangshan <jiangshanlai@...il.com>
Cc: Anish Ghulati <aghulati@...gle.com>, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, Paolo Bonzini <pbonzini@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
hpa@...or.com, Vitaly Kuznetsov <vkuznets@...hat.com>,
peterz@...radead.org, paulmck@...nel.org,
Mark Rutland <mark.rutland@....com>,
Venkatesh Srinivas <venkateshs@...omium.org>
Subject: Re: [RFC PATCH 09/14] KVM: x86: Move shared KVM state into VAC
On Fri, Nov 17, 2023, Lai Jiangshan wrote:
> On Wed, Nov 8, 2023 at 4:21 AM Anish Ghulati <aghulati@...gle.com> wrote:
> >
> > From: Venkatesh Srinivas <venkateshs@...omium.org>
> >
> > Move kcpu_kick_mask and vm_running_vcpu* from arch neutral KVM code into
> > VAC.
>
> Hello, Venkatesh, Anish
>
> IMO, the allocation code for cpu_kick_mask has to be moved too.
I'm pretty sure this patch should be dropped. I can't think of any reason why
cpu_kick_mask needs to be in VAC, and kvm_running_vcpu definitely needs to be
per-KVM.
Powered by blists - more mailing lists