From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH/RFC] KVM: track pid for VCPU only on KVM_RUN ioctl Date: Tue, 19 Aug 2014 12:03:20 +0200 Message-ID: <53F320E8.3040502@redhat.com> References: <1407249854-2953-1-git-send-email-borntraeger@de.ibm.com> <53E38193.8060206@redhat.com> <53F30CF3.5030606@de.ibm.com> <53F3187E.6080706@redhat.com> <53F31D35.4010901@de.ibm.com> <53F31E9F.9020402@redhat.com> <53F32005.2060902@de.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: KVM , Gleb Natapov , Rik van Riel , Raghavendra K T , Michael Mueller To: Christian Borntraeger Return-path: Received: from mx1.redhat.com ([209.132.183.28]:7415 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750767AbaHSKDf (ORCPT ); Tue, 19 Aug 2014 06:03:35 -0400 In-Reply-To: <53F32005.2060902@de.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: Il 19/08/2014 11:59, Christian Borntraeger ha scritto: > Its only for the interrupts that are cpu local (like pending IPIs). > In addition, we would do that only for the reset case (with an > interface that can be used for migration). Right now > KVM_S390_INITIAL_RESET takes the vcpu_mutex, so this protects against > KVM_RUN. I'm not sure, this does seem like a workaround for another limitation after all... Gleb? Paolo