LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@redhat.com> To: Paolo Bonzini <pbonzini@redhat.com> Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org, Nadav Amit <namit@cs.technion.ac.il>, Gleb Natapov <gleb@kernel.org> Subject: Re: [PATCH 0/8] KVM: minor APIC fixes and cleanups Date: Fri, 30 Jan 2015 16:20:31 +0100 [thread overview] Message-ID: <20150130152031.GC28519@potion.redhat.com> (raw) In-Reply-To: <54CB4D44.1080109@redhat.com> 2015-01-30 10:22+0100, Paolo Bonzini: > On 29/01/2015 22:48, Radim Krčmář wrote: > > This patch series is made our of three logical parts, > > > > [1-3/8] are just a cleanup and could be omitted > > [4-6/8] improve broadcast detection and unoptimized delivery > > [7-8/8] handle mixed mode (by falling back to improvements from [5-6/9]) > > I applied patches 1-4 and commented on patch 5. > > I'm afraid that patches 7-8 could lead to missed optimizations in some cases. True, I'll do more research on complexity of its assembly. > Regarding patch 6, perhaps there's a way to avoid this: > > + /* XXX: A superset of x2APIC broadcasts is fine in practice as long as > + * we don't support APIC ID > 0xfeffffff. > + */ > > It's ugly. :) Yeah, there is: don't deliver x2APIC broadcasts to xAPIC. (I'm not even sure if it is correct ...) Without that delivery, we could do something like if (irq->dest_id == (x2apic_ipi ? X2APIC_BROADCAST : APIC_BROADCAST))
next prev parent reply other threads:[~2015-01-30 15:20 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-29 21:48 [PATCH 0/8] KVM: minor APIC fixes and cleanups Radim Krčmář 2015-01-29 21:48 ` [PATCH 1/8] KVM: x86: return bool from kvm_apic_match*() Radim Krčmář 2015-01-29 22:10 ` Joe Perches 2015-01-30 8:50 ` Paolo Bonzini 2015-01-29 21:48 ` [PATCH 2/8] KVM: x86: cleanup kvm_apic_match_*() Radim Krčmář 2015-01-30 8:52 ` Paolo Bonzini 2015-01-30 13:06 ` Radim Krčmář 2015-02-02 14:26 ` Radim Krčmář 2015-02-02 14:28 ` Paolo Bonzini 2015-02-02 14:30 ` Radim Krčmář 2015-02-02 14:29 ` Radim Krčmář 2015-01-29 21:48 ` [PATCH 3/8] KVM: x86: replace 0 with APIC_DEST_PHYSICAL Radim Krčmář 2015-01-29 21:48 ` [PATCH 4/8] KVM: x86: fix x2apic logical address matching Radim Krčmář 2015-01-29 21:48 ` [PATCH 5/8] KVM: x86: use MDA for interrupt matching Radim Krčmář 2015-01-30 9:03 ` Paolo Bonzini 2015-01-30 13:09 ` Radim Krčmář 2015-01-29 21:48 ` [PATCH 6/8] KVM: x86: allow mixed APIC mode broadcast Radim Krčmář 2015-01-29 21:48 ` [PATCH 7/8] KVM: x86: avoid logical_map when it is invalid Radim Krčmář 2015-01-30 9:19 ` Paolo Bonzini 2015-01-30 14:21 ` Radim Krčmář 2015-01-30 14:21 ` Paolo Bonzini 2015-01-30 9:38 ` Paolo Bonzini 2015-01-30 14:56 ` Radim Krčmář 2015-01-30 15:10 ` Paolo Bonzini 2015-01-30 17:09 ` Radim Krčmář 2015-01-29 21:48 ` [PATCH 8/8] KVM: x86: simplify kvm_apic_map Radim Krčmář 2015-01-30 9:18 ` Paolo Bonzini 2015-01-30 15:14 ` Radim Krčmář 2015-01-30 15:23 ` Paolo Bonzini 2015-01-30 16:57 ` Radim Krčmář 2015-01-30 21:15 ` Paolo Bonzini 2015-01-30 9:22 ` [PATCH 0/8] KVM: minor APIC fixes and cleanups Paolo Bonzini 2015-01-30 15:20 ` Radim Krčmář [this message] 2015-01-30 15:24 ` 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=20150130152031.GC28519@potion.redhat.com \ --to=rkrcmar@redhat.com \ --cc=gleb@kernel.org \ --cc=kvm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --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: linkBe 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).