| Date | Fri, 20 Dec 2019 11:04:45 +0100 | From | Cornelia Huck <> | Subject | Re: [PATCH v2 35/45] KVM: s390: Manually invoke vcpu setup during kvm_arch_vcpu_create() |
| |
On Wed, 18 Dec 2019 13:55:20 -0800 Sean Christopherson <sean.j.christopherson@intel.com> wrote:
> Rename kvm_arch_vcpu_setup() to kvm_s390_vcpu_setup() and manually call > the new function during kvm_arch_vcpu_create(). Define an empty > kvm_arch_vcpu_setup() as it's still required for compilation. This > is effectively a nop as kvm_arch_vcpu_create() and kvm_arch_vcpu_setup() > are called back-to-back by common KVM code. Obsoleting > kvm_arch_vcpu_setup() paves the way for its removal. > > Note, gmap_remove() is now called if setup fails, as s390 was previously > freeing it via kvm_arch_vcpu_destroy(), which is called by common KVM > code if kvm_arch_vcpu_setup() fails.
Yes, this looks like the only thing that needs to be undone (sca_add_vcpu() is done later in the process.)
Maybe mention that gmap_remove() is for ucontrol only? I was confused for a moment :)
> > No functional change intended. > > Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com> > --- > arch/s390/kvm/kvm-s390.c | 11 +++++++++++ > 1 file changed, 11 insertions(+)
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
|