lkml.org 
[lkml]   [2022]   [Jun]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH 4/7] KVM: x86: SVM: fix avic_kick_target_vcpus_fast
From
Date
On Wed, 2022-06-08 at 15:21 +0200, Paolo Bonzini wrote:
> On 6/6/22 20:08, Maxim Levitsky wrote:
> > There are two issues in avic_kick_target_vcpus_fast
> >
> > 1. It is legal to issue an IPI request with APIC_DEST_NOSHORT
> > and a physical destination of 0xFF (or 0xFFFFFFFF in case of x2apic),
> > which must be treated as a broadcast destination.
> >
> > Fix this by explicitly checking for it.
> > Also don’t use ‘index’ in this case as it gives no new information.
> >
> > 2. It is legal to issue a logical IPI request to more than one target.
> > Index field only provides index in physical id table of first
> > such target and therefore can't be used before we are sure
> > that only a single target was addressed.
> >
> > Instead, parse the ICRL/ICRH, double check that a unicast interrupt
> > was requested, and use that info to figure out the physical id
> > of the target vCPU.
> > At that point there is no need to use the index field as well.
> >
> >
> > In addition to fixing the above issues, also skip the call to
> > kvm_apic_match_dest.
> >
> > It is possible to do this now, because now as long as AVIC is not
> > inhibited, it is guaranteed that none of the vCPUs changed their
> > apic id from its default value.
> >
> >
> > This fixes boot of windows guest with AVIC enabled because it uses
> > IPI with 0xFF destination and no destination shorthand.
> >
> > Fixes: 7223fd2d5338 ("KVM: SVM: Use target APIC ID to complete AVIC IRQs when possible")
> > Cc: stable@vger.kernel.org
> >
> > Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
>
> Is it possible to use kvm_intr_is_single_vcpu_fast, or am I missing
> something?

Yes, except that it needs 'struct kvm_lapic_irq' which we won't have when
we emulate guest<->guest interrupts, and also it goes over apic map and such,
which can be be skipped.

It also does more unneeded things like dealing with low priority mode for example,
which thankfully AVIC doenst' support and if attempted will still VM exit
with 'incomplete IPI' but with AVIC_IPI_FAILURE_INVALID_INT_TYPE subreason,
which goes through full APIC register emulation.

I do think about the fact that ICRL/H parsing in the case of logical ID,
(which depends on cluser mode and x2apic mode) can be moved to some common
code, but I wasn't able yet to find a clean way to do it.

BTW: there is another case where AVIC must be inhibited: in xapic mode,
logical ids, don't have to have a single bit set in the mask area of the logical id,
(low 4 bits in cluster mode and all 8 bits in flat mode)
and neither there is a guarnantee that multilple CPUs don't share these bits.

AVIC however has a logical ID table which maps each (bit x cluster value) to a physical id,
and therefore a single vCPU, so tha later is not possible to support with AVIC.

I haven't studied the code that is responsible for this, I will do this soon.


Thankfully IPIv only supports physical IPI mode (this is what I heard, don't know for sure).

I also will write a unit test for this very soon, to test various logical id
IPIs, messing with logical id registers, etc, etc.

Best regards,
Maxim Levitsky


>
> Series queued, thanks.
>
> Paolo
>


\
 
 \ /
  Last update: 2022-06-09 10:14    [W:0.085 / U:0.728 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site