From: Paolo Bonzini <pbonzini@redhat.com>
To: "Radim Krčmář" <rkrcmar@redhat.com>, linux-kernel@vger.kernel.org
Cc: kvm@vger.kernel.org, Gleb Natapov <gleb@kernel.org>,
Nadav Amit <namit@cs.technion.ac.il>
Subject: Re: [PATCH 0/4] KVM: x86: APIC fixes
Date: Mon, 01 Dec 2014 17:22:16 +0100 [thread overview]
Message-ID: <547C95B8.7020300@redhat.com> (raw)
In-Reply-To: <1417114994-25235-1-git-send-email-rkrcmar@redhat.com>
On 27/11/2014 20:03, Radim Krčmář wrote:
> The interesting one is [3/4], which improves upon a previous CVE fix;
> we also handle logical destination wrapping in it, so [2/4] does the
> same for physical; and to make it nicer, [1/4] removes a condition.
> [4/4] makes our fast path return true when the message was handled.
>
> Radim Krčmář (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?
Paolo
next prev parent reply other threads:[~2014-12-01 16:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 19:03 [PATCH 0/4] KVM: x86: APIC fixes Radim Krčmář
2014-11-27 19:03 ` [PATCH 1/4] KVM: x86: deliver phys lowest-prio Radim Krčmář
2014-11-27 19:03 ` [PATCH 2/4] KVM: x86: fix APIC physical destination wrapping Radim Krčmář
2014-11-27 19:03 ` [PATCH 3/4] KVM: x86: allow 256 logical x2APICs again Radim Krčmář
2014-11-27 19:53 ` Nadav Amit
2014-11-27 20:16 ` Radim Krčmář
2014-11-27 20:39 ` Nadav Amit
2014-11-27 21:03 ` Radim Krčmář
2014-11-27 19:03 ` [PATCH 4/4] KVM: x86: don't retry hopeless APIC delivery Radim Krčmář
2014-11-27 22:30 ` [PATCH 5/4] KVM: x86: check bounds of APIC maps Radim Krčmář
2014-12-01 16:22 ` Paolo Bonzini [this message]
2014-12-01 17:55 ` [PATCH 0/4] KVM: x86: APIC fixes Radim Krčmář
2014-12-01 17:56 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=547C95B8.7020300@redhat.com \
--to=pbonzini@redhat.com \
--cc=gleb@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namit@cs.technion.ac.il \
--cc=rkrcmar@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox