From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932573AbdBGWCo (ORCPT ); Tue, 7 Feb 2017 17:02:44 -0500 Received: from mx1.redhat.com ([209.132.183.28]:55544 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932101AbdBGWCm (ORCPT ); Tue, 7 Feb 2017 17:02:42 -0500 Date: Tue, 7 Feb 2017 22:52:18 +0100 From: Radim =?utf-8?B?S3LEjW3DocWZ?= To: Paolo Bonzini Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org Subject: Re: [PATCH v2 0/6] KVM: x86: cleanup and speedup for APICv Message-ID: <20170207215217.GG31091@potion> References: <1482164232-130035-1-git-send-email-pbonzini@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Tue, 07 Feb 2017 21:52:21 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 2017-02-07 18:23+0100, Paolo Bonzini: > On 19/12/2016 17:17, Paolo Bonzini wrote: >> These are the fixed patches that now pass vmx.flat. The issue in >> "KVM: x86: do not scan IRR twice on APICv vmentry" was that, >> in v1 of the patches, kvm_cpu_get_interrupt did not scan IRR >> at all if it found PIR.ON=0. This is now fixed in patches 4 and 5. >> >> Another latent bug has to be fixed in patch 2. The patch also >> highlights the maze that check_nested_events has become. Fixing >> that is left for later. >> >> The patches are on top of the (non-APICv-related) KVM_REQ_EVENT >> patches from this morning. According to kvm-unit-tests, patch 6 speeds >> up self-IPIs (if not done through the accelerated self-IPI MSR) by 5-10%. >> >> Paolo > > Ping? I think the patches are ready to be applied -- there might be some rough edges with nested, but it was broken even before, and they fix at least one known bug.