Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: kvm@vger.kernel.org, x86@kernel.org,
	Paolo Bonzini <pbonzini@redhat.com>,
	Sean Christopherson <sean.j.christopherson@intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Andy Lutomirski <luto@kernel.org>
Subject: Re: [PATCH 2/2] x86/kvm: don't forget to ACK async PF IRQ
Date: Wed, 09 Sep 2020 10:49:27 +0200	[thread overview]
Message-ID: <878sdjmj1k.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <20200909081613.GB2446260@gmail.com>

Ingo Molnar <mingo@kernel.org> writes:

> * Vitaly Kuznetsov <vkuznets@redhat.com> wrote:
>
>> Merge commit 26d05b368a5c0 ("Merge branch 'kvm-async-pf-int' into HEAD")
>> tried to adapt the new interrupt based async PF mechanism to the newly
>> introduced IDTENTRY magic but unfortunately it missed the fact that
>> DEFINE_IDTENTRY_SYSVEC() doesn't call ack_APIC_irq() on its own and
>> all DEFINE_IDTENTRY_SYSVEC() users have to call it manually.
>> 
>> As the result all multi-CPU KVM guest hang on boot when
>> KVM_FEATURE_ASYNC_PF_INT is present. The breakage went unnoticed because no
>> KVM userspace (e.g. QEMU) currently set it (and thus async PF mechanism
>> is currently disabled) but we're about to change that.
>> 
>> Fixes: 26d05b368a5c0 ("Merge branch 'kvm-async-pf-int' into HEAD")
>> Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
>
> This also fixes a kvmtool regression, but interestingly it does not set 
> KVM_FEATURE_ASYNC_PF_INT either AFAICS:
>
>   kepler:~/kvmtool.git> git grep KVM_FEATURE_ASYNC_PF_INT
>   kepler:~/kvmtool.git> 

My wild guess would be that kvmtool doesn't manually set any of the KVM
PV features:

[vitty@vitty kvmtool]$ git grep KVM_FEATURE_
[vitty@vitty kvmtool]$ 

it just blindly passes whatever it gets from KVM via
KVM_GET_SUPPORTED_CPUID to KVM_SET_CPUID2 and KVM_FEATURE_ASYNC_PF_INT
among other PV features is set there by default.

>
>   kepler:~/kvmtool.git> grep url .git/config
> 	url = https://git.kernel.org/pub/scm/linux/kernel/git/will/kvmtool.git
>
> So either I missed the flag-setting in the kvmtools.git source, or maybe 
> there's some other way to trigger this bug?
>
> Anyway, please handle this as a v5.9 regression:
>
> 	Tested-by: Ingo Molnar <mingo@kernel.org>

Thanks!

-- 
Vitaly


  reply	other threads:[~2020-09-09  8:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-08 13:53 [PATCH 0/2] x86/kvm: fix interrupts based APF mechanism Vitaly Kuznetsov
2020-09-08 13:53 ` [PATCH 1/2] x86/kvm: properly use DEFINE_IDTENTRY_SYSVEC() macro Vitaly Kuznetsov
2020-09-08 13:53 ` [PATCH 2/2] x86/kvm: don't forget to ACK async PF IRQ Vitaly Kuznetsov
2020-09-09  8:16   ` Ingo Molnar
2020-09-09  8:49     ` Vitaly Kuznetsov [this message]
2020-09-12  6:22       ` 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=878sdjmj1k.fsf@vitty.brq.redhat.com \
    --to=vkuznets@redhat.com \
    --cc=bp@alien8.de \
    --cc=kvm@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=sean.j.christopherson@intel.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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