From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH 0/4] KVM: x86: APIC fixes Date: Mon, 01 Dec 2014 18:56:22 +0100 Message-ID: <547CABC6.7030309@redhat.com> References: <1417114994-25235-1-git-send-email-rkrcmar@redhat.com> <547C95B8.7020300@redhat.com> <20141201175505.GA22851@potion.brq.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org, Gleb Natapov , Nadav Amit To: =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= Return-path: In-Reply-To: <20141201175505.GA22851@potion.brq.redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 01/12/2014 18:55, Radim Kr=C4=8Dm=C3=A1=C5=99 wrote: > 2014-12-01 17:22+0100, Paolo Bonzini: >> On 27/11/2014 20:03, Radim Kr=C4=8Dm=C3=A1=C5=99 wrote: >>> The interesting one is [3/4], which improves upon a previous CVE fi= x; >>> we also handle logical destination wrapping in it, so [2/4] does th= e >>> same for physical; and to make it nicer, [1/4] removes a condition= =2E >>> [4/4] makes our fast path return true when the message was handled. >>> >>> Radim Kr=C4=8Dm=C3=A1=C5=99 (4): >>> KVM: x86: deliver phys lowest-prio >>> KVM: x86: fix APIC physical destination wrapping >>> KVM: x86: allow 256 logical x2APICs again >>> KVM: x86: don't retry hopeless APIC delivery >>> >>> arch/x86/kvm/lapic.c | 20 +++++++++++--------- >>> arch/x86/kvm/lapic.h | 2 -- >>> 2 files changed, 11 insertions(+), 11 deletions(-) >>> >> >> So the order should be 1/2/5/3/4, right? >=20 > It would be safer, thank you. >=20 > (And when I look at it now, [4/4] would be better as 1st.) Ok, applying 4/1/2/5/3. Paolo