From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Sami Farin <lkml20261027@mifar.in>,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@kernel.org>,
kvm@vger.kernel.org, kimjw04271234@gmail.com,
stable@vger.kernel.org
Subject: Re: [REGRESSION] KVM: x86: OVMF boot hang with SMM enabled after commit b3e6212dea2e ("KVM: x86: Use active memslots for the per-vCPU MMIO cache")
Date: Wed, 28 Oct 2026 19:42:38 +0100 [thread overview]
Message-ID: <6f6694db-b1aa-4d9e-be82-b0d11cd814d9@redhat.com> (raw)
In-Reply-To: <auI4kViOXpqxT3wA@google.com>
On 10/28/26 19:01, Sean Christopherson wrote:
> 2. 'trace-cmd stream -e kvm:kvm_exit' shows a storm of 32-bit IN reads on port 0x608
> (the ICH9 ACPI PM timer):
> kvm_exit: reason IO_INSTRUCTION rip 0x7b125f0c info 608000b 0
This is already too late - the problem happened earlier.
>>> vcpu_cache_mmio_info() does not use the address space id:
>>>
>>> u64 gen = kvm_memslots(vcpu->kvm)->generation;
>>>
>>> Will send a patch soon.
>> Nevermind, wrong tree - I was reinventing the (apparently buggy) commit
>> because it's past 7.3.0-rc7... still looking.
> Heh, I did the same thing. I was like, "this code doesn't exist!!!", then
> realized the commit isn't in kvm/next.
I'll try to reproduce tomorrow. Sami, can you check
1) if this patch gives the WARN (with vanilla 6.18.58):
diff --git a/arch/x86/kvm/x86.h b/arch/x86/kvm/x86.h
index cfe96962a4e4..a96d839a317b 100644
--- a/arch/x86/kvm/x86.h
+++ b/arch/x86/kvm/x86.h
@@ -263,6 +263,7 @@ static inline void vcpu_cache_mmio_info(struct
kvm_vcpu *vcpu,
vcpu->arch.mmio_access = access;
vcpu->arch.mmio_gfn = gfn;
vcpu->arch.mmio_gen = gen;
+ WARN_ON_ONCE((gen & 1) != kvm_arch_vcpu_memslots_id(vcpu));
}
static inline bool vcpu_match_mmio_gen(struct kvm_vcpu *vcpu)
2) if patch 1 or patch 2 separately are enough to fix the issue;
If you have time, can you also check if it fails to boot even before
reaching Windows (you can try any Linux ISO, or even with no disk at
all)? Also, just to cover all bases is your machine Intel or AMD?
Thanks,
Paolo
next prev parent reply other threads:[~2026-10-28 18:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2026102314-CVE-2026-99082-e5b1@gregkh>
2026-10-27 12:41 ` Sami Farin
2026-10-28 17:37 ` Sean Christopherson
2026-10-28 17:48 ` Paolo Bonzini
2026-10-28 17:58 ` Paolo Bonzini
2026-10-28 18:01 ` Sean Christopherson
2026-10-28 18:42 ` Paolo Bonzini [this message]
2026-10-29 10:38 ` Sami Farin
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=6f6694db-b1aa-4d9e-be82-b0d11cd814d9@redhat.com \
--to=pbonzini@redhat.com \
--cc=gregkh@kernel.org \
--cc=kimjw04271234@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml20261027@mifar.in \
--cc=seanjc@google.com \
--cc=stable@vger.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
all inboxes | Powered by JetHome®