From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932717AbcGHQaT (ORCPT ); Fri, 8 Jul 2016 12:30:19 -0400 Received: from mx1.redhat.com ([209.132.183.28]:48286 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932159AbcGHQaM (ORCPT ); Fri, 8 Jul 2016 12:30:12 -0400 Subject: Re: [PATCH v2 00/13] KVM: x86: break the xAPIC barrier To: =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , linux-kernel@vger.kernel.org, kvm@vger.kernel.org References: <20160707171550.14675-1-rkrcmar@redhat.com> <20160708162907.GB10741@potion> Cc: "Lan, Tianyu" , Igor Mammedov , Jan Kiszka , Peter Xu From: Paolo Bonzini Message-ID: <9907d558-57bb-f85d-15ec-2b77da8df59d@redhat.com> Date: Fri, 8 Jul 2016 18:30:07 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <20160708162907.GB10741@potion> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Fri, 08 Jul 2016 16:30:11 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 08/07/2016 18:29, Radim Krčmář wrote: > NACK, sorry. > > KVM allows x2APIC even without interrupt remapping and therefore > interprets IOAPIC destination 0xff as a broadcast, which causes a bug > when x2APIC uses 0xff. > > I'll fix that in v3. The hack will be disabled when x2apic_api > capability is enabled. Right, I was going to suggest the same. It's fine, just provide patch(es) on top and I can squash them. Paolo