From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49489) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZkZzH-0001wT-EC for qemu-devel@nongnu.org; Fri, 09 Oct 2015 11:53:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZkZzD-0003cj-1t for qemu-devel@nongnu.org; Fri, 09 Oct 2015 11:53:39 -0400 Received: from relay.parallels.com ([195.214.232.42]:51879) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZkZzC-0003Yn-4g for qemu-devel@nongnu.org; Fri, 09 Oct 2015 11:53:34 -0400 Date: Fri, 9 Oct 2015 18:53:09 +0300 From: Roman Kagan Message-ID: <20151009155307.GU27239@rkaganb.sw.ru> References: <1444397988-20167-1-git-send-email-den@openvz.org> <1444397988-20167-2-git-send-email-den@openvz.org> <5617D259.8070101@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <5617D259.8070101@redhat.com> Subject: Re: [Qemu-devel] [PATCH 1/2] kvm/x86: Hyper-V synthetic interrupt controller List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Gleb Natapov , qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org, Christian Borntraeger , Andrey Smetanin , "Denis V. Lunev" , Vitaly Kuznetsov , "K. Y. Srinivasan" On Fri, Oct 09, 2015 at 04:42:33PM +0200, Paolo Bonzini wrote: > You need to add SYNIC vectors to the EOI exit bitmap, so that APICv > (Xeon E5 or higher, Ivy Bridge or newer) is handled correctly. You also > need to check the auto EOI exit bitmap in __apic_accept_irq, and avoid > going through kvm_x86_ops->deliver_posted_interrupt for auto EOI > vectors. Something like > > if (kvm_x86_ops->deliver_posted_interrupt && > !test_bit(...)) > > in place of the existing "if (kvm_x86_ops->deliver_posted_interrupt)". Indeed, missed that path, thanks! > I really don't like this auto-EOI extension, but I guess that's the > spec. :( If it wasn't for it, you could do everything very easily in > userspace using Google's proposed MSR exit. I guess you're right. We'd probably have to (ab)use MSI for SINT delivery, though. Anyway the need to implement auto-EOI rules that out. Thanks for the quick review, we'll try to address your comments in the next round. Roman.