Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753896AbbKBQIN (ORCPT ); Mon, 2 Nov 2015 11:08:13 -0500 Received: from mx1.redhat.com ([209.132.183.28]:40700 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753003AbbKBQIH (ORCPT ); Mon, 2 Nov 2015 11:08:07 -0500 Subject: Re: [PATCH 1/3] KVM: x86: merge kvm_arch_set_irq with kvm_set_msi_inatomic To: Radim Krcmar References: <1446466878-32837-1-git-send-email-pbonzini@redhat.com> <1446466878-32837-2-git-send-email-pbonzini@redhat.com> <20151102145923.GB24667@potion.brq.redhat.com> Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org, Alex Williamson From: Paolo Bonzini Message-ID: <56378A62.3090706@redhat.com> Date: Mon, 2 Nov 2015 17:08:02 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <20151102145923.GB24667@potion.brq.redhat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 962 Lines: 23 On 02/11/2015 15:59, Radim Krcmar wrote: > > We do not want to do too much work in atomic context, in particular > > not walking all the VCPUs of the virtual machine. So we want > > to distinguish the architecture-specific injection function for irqfd > > from kvm_set_msi. Since it's still empty, reuse the newly added > > kvm_arch_set_irq and rename it to kvm_arch_set_irq_inatomic. > > kvm/queue uses kvm_arch_set_irq since b7184313f4b9 ("kvm/x86: Hyper-V > synthetic interrupt controller"). > > Is synic going to be dropped before this patch is merged? Yes. Both because the Virtuozzo people confirmed that kvm_arch_set_irq isn't needed for synic, and because synic is currently broken with APICv. Paolo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/