[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e57e11f4-ec24-6ad1-22ce-97da1910ed02@redhat.com>
Date: Sat, 2 Nov 2019 11:01:04 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: "Suthikulpanit, Suravee" <Suravee.Suthikulpanit@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>
Cc: "rkrcmar@...hat.com" <rkrcmar@...hat.com>,
"joro@...tes.org" <joro@...tes.org>,
"vkuznets@...hat.com" <vkuznets@...hat.com>,
"rkagan@...tuozzo.com" <rkagan@...tuozzo.com>,
"graf@...zon.com" <graf@...zon.com>,
"jschoenh@...zon.de" <jschoenh@...zon.de>,
"karahmed@...zon.de" <karahmed@...zon.de>,
"rimasluk@...zon.com" <rimasluk@...zon.com>,
"Grimm, Jon" <Jon.Grimm@....com>
Subject: Re: [PATCH v4 12/17] svm: Temporary deactivate AVIC during ExtINT
handling
On 01/11/19 23:41, Suthikulpanit, Suravee wrote:
> + /*
> + * IRQ window is not needed when AVIC is enabled,
> + * unless we have pending ExtINT since it cannot be injected
> + * via AVIC. In such case, we need to temporarily disable AVIC,
> + * and fallback to injecting IRQ via V_IRQ.
> + */
> + if (kvm_vcpu_apicv_active(vcpu))
> + svm_request_update_avic(vcpu, false);
This must be pretty heavy-weight on SMP VMs, even if most ExtINT guests
do not need SMP in the guest. One alternative is to enable/disable
APICv when LVT or IOAPIC registers are written with ExtINT mode. Not a
blocker, just an idea to consider.
Paolo
Powered by blists - more mailing lists