mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Maxim Levitsky <mlevitsk@redhat.com>
To: Sean Christopherson <seanjc@google.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
	Li RongQing <lirongqing@baidu.com>
Subject: Re: [PATCH 12/19] KVM: x86: Disable APIC logical map if logical ID covers multiple MDAs
Date: Wed, 31 Aug 2022 16:23:32 +0300	[thread overview]
Message-ID: <bccb116fd8fef3da918faa2270fac3256bfb62c6.camel@redhat.com> (raw)
In-Reply-To: <20220831003506.4117148-13-seanjc@google.com>

On Wed, 2022-08-31 at 00:34 +0000, Sean Christopherson wrote:
> Disable the optimized APIC logical map if a logical ID covers multiple
> MDAs, i.e. if a vCPU has multiple bits set in its ID.  In logical mode,
> events match if "ID & MDA != 0", i.e. creating an entry for only the
> first bit can cause interrupts to be missed.
> 
> Note, creating an entry for every bit is also wrong as KVM would generate
> IPIs for every matching bit.  It would be possible to teach KVM to play
> nice with this edge case, but it is very much an edge case and probably
> not used in any real world OS, i.e. it's not worth optimizing.
> 
> Use an impossible value for the "mode" to effectively designate that it's
> disabled.  Don't bother adding a dedicated "invalid" value, the mode
> handling will be cleaned up in the future and it would take just as much
> effort to explain what value is "safe" at this time.
> 
> Fixes: 1e08ec4a130e ("KVM: optimize apic interrupt delivery")
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> ---
>  arch/x86/kvm/lapic.c | 11 +++++++++--
>  1 file changed, 9 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c
> index 9dda989a1cf0..82278acae95b 100644
> --- a/arch/x86/kvm/lapic.c
> +++ b/arch/x86/kvm/lapic.c
> @@ -300,8 +300,15 @@ void kvm_recalculate_apic_map(struct kvm *kvm)
>  		if (!kvm_apic_map_get_logical_dest(new, ldr, &cluster, &mask))
>  			continue;
>  
> -		if (mask)
> -			cluster[ffs(mask) - 1] = apic;
> +		if (!mask)
> +			continue;
> +
> +		if (!is_power_of_2(mask)) {
> +			new->mode = KVM_APIC_MODE_XAPIC_FLAT |
> +				    KVM_APIC_MODE_XAPIC_CLUSTER;
> +			continue;
> +		}
> +		cluster[ffs(mask) - 1] = apic;
>  	}
>  out:
>  	old = rcu_dereference_protected(kvm->arch.apic_map,


I was about to complain about the abuse of the invalid mode,
but I see that this is fixed in later patch as it is said in the commit
description, so no complains.

Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com>

Best regards,
	Maxim Levitsky


  reply	other threads:[~2022-08-31 13:23 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-31  0:34 [PATCH 00/19] KVM: x86: AVIC and local APIC fixes+cleanups Sean Christopherson
2022-08-31  0:34 ` [PATCH 01/19] KVM: SVM: Process ICR on AVIC IPI delivery failure due to invalid target Sean Christopherson
2022-08-31  9:18   ` Maxim Levitsky
2022-08-31  0:34 ` [PATCH 02/19] KVM: SVM: Don't put/load AVIC when setting virtual APIC mode Sean Christopherson
2022-08-31  9:24   ` Maxim Levitsky
2022-08-31 16:33     ` Sean Christopherson
2022-08-31  0:34 ` [PATCH 03/19] Revert "KVM: SVM: Introduce hybrid-AVIC mode" Sean Christopherson
2022-08-31  5:59   ` Maxim Levitsky
2022-08-31  6:45     ` Maxim Levitsky
2022-08-31 16:29       ` Sean Christopherson
2022-08-31 17:46         ` Maxim Levitsky
2022-08-31 17:58           ` Jim Mattson
2022-08-31 18:01             ` Maxim Levitsky
2022-08-31 19:12           ` Sean Christopherson
2022-09-01 10:25             ` Maxim Levitsky
2022-09-01 11:47               ` Jim Mattson
2022-09-01 13:29               ` Sean Christopherson
2022-09-01 13:53               ` Sean Christopherson
2022-09-01 15:08               ` Sean Christopherson
2022-08-31 16:19     ` Sean Christopherson
2022-08-31 17:47       ` Maxim Levitsky
2022-08-31  0:34 ` [PATCH 04/19] KVM: SVM: Replace "avic_mode" enum with "x2avic_enabled" boolean Sean Christopherson
2022-08-31  9:36   ` Maxim Levitsky
2022-08-31  0:34 ` [PATCH 05/19] KVM: SVM: Compute dest based on sender's x2APIC status for AVIC kick Sean Christopherson
2022-08-31  9:38   ` Maxim Levitsky
2022-09-01  2:56   ` Li,Rongqing
2022-08-31  0:34 ` [PATCH 06/19] KVM: SVM: Get x2APIC logical dest bitmap from ICRH[15:0], not ICHR[31:16] Sean Christopherson
2022-08-31  6:09   ` Maxim Levitsky
2022-08-31  9:43     ` Maxim Levitsky
2022-08-31 16:35       ` Sean Christopherson
2022-08-31 18:18         ` Maxim Levitsky
2022-08-31  0:34 ` [PATCH 07/19] KVM: SVM: Drop buggy and redundant AVIC "single logical dest" check Sean Christopherson
2022-08-31  6:19   ` Maxim Levitsky
2022-08-31 16:37     ` Sean Christopherson
2022-08-31 18:10       ` Maxim Levitsky
2022-08-31  0:34 ` [PATCH 08/19] KVM: SVM: Remove redundant cluster calculation that also creates a shadow Sean Christopherson
2022-08-31 10:19   ` Maxim Levitsky
2022-09-01 20:02     ` Sean Christopherson
2022-08-31  0:34 ` [PATCH 09/19] KVM: SVM: Drop duplicate calcuation of AVIC/x2AVIC "logical index" Sean Christopherson
2022-08-31  0:34 ` [PATCH 10/19] KVM: SVM: Document that vCPU ID == APIC ID in AVIC kick fastpatch Sean Christopherson
2022-08-31 10:22   ` Maxim Levitsky
2022-08-31 16:16     ` Sean Christopherson
2022-08-31 17:49       ` Maxim Levitsky
2022-08-31  0:34 ` [PATCH 11/19] KVM: SVM: Add helper to perform final AVIC "kick" of single vCPU Sean Christopherson
2022-08-31 10:25   ` Maxim Levitsky
2022-08-31 15:08     ` Sean Christopherson
2022-08-31 18:12       ` Maxim Levitsky
2022-08-31  0:34 ` [PATCH 12/19] KVM: x86: Disable APIC logical map if logical ID covers multiple MDAs Sean Christopherson
2022-08-31 13:23   ` Maxim Levitsky [this message]
2022-08-31  0:35 ` [PATCH 13/19] KVM: x86: Disable APIC logical map if vCPUs are aliased in logical mode Sean Christopherson
2022-08-31 13:24   ` Maxim Levitsky
2022-08-31  0:35 ` [PATCH 14/19] KVM: x86: Honor architectural behavior for aliased 8-bit APIC IDs Sean Christopherson
2022-08-31 13:37   ` Maxim Levitsky
2022-08-31 16:41     ` Sean Christopherson
2022-08-31 17:51       ` Maxim Levitsky
2022-08-31  0:35 ` [PATCH 15/19] KVM: x86: Explicitly skip optimized logical map setup if vCPU's LDR==0 Sean Christopherson
2022-08-31 13:41   ` Maxim Levitsky
2022-08-31 16:47     ` Sean Christopherson
2022-08-31  0:35 ` [PATCH 16/19] KVM: x86: Explicitly track all possibilities for APIC map's logical modes Sean Christopherson
2022-08-31 13:43   ` Maxim Levitsky
2022-08-31 16:56     ` Sean Christopherson
2022-08-31 17:53       ` Maxim Levitsky
2022-09-16 18:58         ` Sean Christopherson
2022-08-31 18:42   ` Maxim Levitsky
2022-08-31 19:17     ` Sean Christopherson
2022-08-31  0:35 ` [PATCH 17/19] KVM: SVM: Handle multiple logical targets in AVIC kick fastpath Sean Christopherson
2022-08-31 13:57   ` Maxim Levitsky
2022-08-31 18:19     ` Sean Christopherson
2022-08-31 18:25       ` Maxim Levitsky
2022-08-31  0:35 ` [PATCH 18/19] KVM: SVM: Ignore writes to Remote Read Data on AVIC write traps Sean Christopherson
2022-08-31 10:40   ` Maxim Levitsky
2022-08-31  0:35 ` [PATCH 19/19] Revert "KVM: SVM: Do not throw warning when calling avic_vcpu_load on a running vcpu" Sean Christopherson
2022-08-31  6:07   ` Maxim Levitsky
2022-08-31  7:03     ` Maxim Levitsky

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=bccb116fd8fef3da918faa2270fac3256bfb62c6.camel@redhat.com \
    --to=mlevitsk@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lirongqing@baidu.com \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=suravee.suthikulpanit@amd.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

all inboxes | Powered by JetHome®