From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Nadav Amit <namit@cs.technion.ac.il>
Cc: pbonzini@redhat.com, kvm@vger.kernel.org, nadav.amit@gmail.com
Subject: Re: [PATCH v2] KVM: x86: some apic broadcast modes does not work
Date: Fri, 3 Oct 2014 14:49:12 +0200 [thread overview]
Message-ID: <20141003124912.GA28730@potion.brq.redhat.com> (raw)
In-Reply-To: <1412285452-27062-1-git-send-email-namit@cs.technion.ac.il>
2014-10-03 00:30+0300, Nadav Amit:
> KVM does not deliver x2APIC broadcast messages with physical mode. Intel SDM
> (10.12.9 ICR Operation in x2APIC Mode) states: "A destination ID value of
> FFFF_FFFFH is used for broadcast of interrupts in both logical destination and
> physical destination modes."
>
> In addition, the local-apic enables cluster mode broadcast. As Intel SDM
> 10.6.2.2 says: "Broadcast to all local APICs is achieved by setting all
> destination bits to one." This patch enables cluster mode broadcast.
>
> The fix tries to combine broadcast in different modes through a unified code.
>
> One rare case occurs when the source of IPI has its APIC disabled. In such
> case, the source can still issue IPIs, but since the source is not obliged to
> have the same LAPIC mode as the enabled ones, we cannot rely on it.
> Since it is a rare case, it is unoptimized and done on the slow-path.
>
> ---
Thanks!
Reviewed-by: Radim Krčmář <rkrcmar@redhat.com>
> Changes v1->v2:
> - Follow Radim's review: setting constants, preferring simplicity to marginal
> performance gain, etc.
> - Combine the cluster mode and x2apic mode patches
>
> Signed-off-by: Nadav Amit <namit@cs.technion.ac.il>
> ---
> diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c
> index b8345dd..ee04adf 100644
> --- a/arch/x86/kvm/lapic.c
> +++ b/arch/x86/kvm/lapic.c
> @@ -68,6 +68,9 @@
> #define MAX_APIC_VECTOR 256
> #define APIC_VECTORS_PER_REG 32
>
> +#define APIC_BROADCAST 0xFF
> +#define X2APIC_BROADCAST 0xFFFFFFFFul
(int is better -- using long introduces an interesting feature with
implicit retyping: (int)X2APIC_BROADCAST != X2APIC_BROADCAST, and we
don't compile with -Wtype-limits to notice it. It poses no problem
now, so I can change it in an inevitable cleanup series / convince lkml
to endorse stricter warnings.)
> +
> #define VEC_POS(v) ((v) & (32 - 1))
> #define REG_POS(v) (((v) >> 5) << 4)
>
> @@ -558,16 +563,25 @@ static void apic_set_tpr(struct kvm_lapic *apic, u32 tpr)
> apic_update_ppr(apic);
> }
>
> -int kvm_apic_match_physical_addr(struct kvm_lapic *apic, u16 dest)
> +static int kvm_apic_broadcast(struct kvm_lapic *apic, u32 dest)
(bool is better.)
> +{
> + return dest == (apic_x2apic_mode(apic) ?
> + X2APIC_BROADCAST : APIC_BROADCAST);
> +}
next prev parent reply other threads:[~2014-10-03 12:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 21:30 [PATCH v2] KVM: x86: some apic broadcast modes does not work Nadav Amit
2014-10-03 12:49 ` Radim Krčmář [this message]
2014-10-06 15:29 ` Nadav Amit
2014-10-06 19:08 ` Radim Krčmář
2014-10-08 8:38 ` Paolo Bonzini
2014-10-08 3:01 ` Wanpeng Li
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=20141003124912.GA28730@potion.brq.redhat.com \
--to=rkrcmar@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=nadav.amit@gmail.com \
--cc=namit@cs.technion.ac.il \
--cc=pbonzini@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;
as well as URLs for NNTP newsgroup(s).