[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z-vvIBP_lENf4Ro8@google.com>
Date: Tue, 1 Apr 2025 06:50:24 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Mikhail Lobanov <m.lobanov@...a.ru>
Cc: Paolo Bonzini <pbonzini@...hat.com>, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
"H. Peter Anvin" <hpa@...or.com>, Maxim Levitsky <mlevitsk@...hat.com>, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, lvc-project@...uxtesting.org
Subject: Re: [PATCH] KVM: x86: forcibly leave SMM mode on vCPU reset
On Tue, Apr 01, 2025, Mikhail Lobanov wrote:
> Hi,
>
> Gentle ping on this patch:
> https://lore.kernel.org/kvm/20250324175707.19925-1-m.lobanov@rosa.ru/
>
> Sent on March 24, still waiting for feedback.
It's in the queue. From Documentation/process/maintainer-kvm-x86.rst:
Timeline
~~~~~~~~
Submissions are typically reviewed and applied in FIFO order, with some wiggle
room for the size of a series, patches that are "cache hot", etc. Fixes,
especially for the current release and or stable trees, get to jump the queue.
Patches that will be taken through a non-KVM tree (most often through the tip
tree) and/or have other acks/reviews also jump the queue to some extent.
Note, the vast majority of review is done between rc1 and rc6, give or take.
The period between rc6 and the next rc1 is used to catch up on other tasks,
i.e. radio silence during this period isn't unusual.
Powered by blists - more mailing lists