From: Sean Christopherson <seanjc@google.com>
To: fuqiang wang <fuqiang.wng@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, Marcelo Tosatti <mtosatti@redhat.com>,
"H . Peter Anvin" <hpa@zytor.com>,
Maxim Levitsky <mlevitsk@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
yu chen <33988979@163.com>, dongxu zhang <xu910121@sina.com>
Subject: Re: [PATCH v5 0/1] KVM: x86: fix some kvm period timer BUG
Date: Mon, 10 Nov 2025 16:28:30 -0800 [thread overview]
Message-ID: <aRKDLo_SFJxyQWG5@google.com> (raw)
In-Reply-To: <20251107034802.39763-1-fuqiang.wng@gmail.com>
On Fri, Nov 07, 2025, fuqiang wang wrote:
> =================================
> Fix both issues in a single patch
> =================================
>
> In versions v2 and v3, I split these two issues into two separate patches
> for fixing. However, this caused patch 2 to revert some of the changes made
> by patch 1.
FWIW, my initial reaction was that I liked splitting this into two patches better,
but after digging through all the angles of this for a few hours, I agree that it's
better to skip the "don't let the delta go negative" patch, because that patch
really only addresses a symptom that shouldn't happen in the first place.
> In patch 4, I attempted to merge the two patches into one and tried to
> describe both issues in the commit message, but I did not do it well. In
> this version, I have included more details in the commit message and the
> cover letter.
next prev parent reply other threads:[~2025-11-11 0:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 3:47 [PATCH v5 0/1] KVM: x86: fix some kvm period timer BUG fuqiang wang
2025-11-07 3:48 ` [PATCH v5 1/1] KVM: x86: Fix VM hard lockup after prolonged suspend with periodic HV timer fuqiang wang
2025-11-11 0:46 ` Sean Christopherson
2025-11-11 8:17 ` fuqiang wang
2025-11-11 0:28 ` Sean Christopherson [this message]
2025-11-11 8:14 ` [PATCH v5 0/1] KVM: x86: fix some kvm period timer BUG fuqiang wang
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=aRKDLo_SFJxyQWG5@google.com \
--to=seanjc@google.com \
--cc=33988979@163.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=fuqiang.wng@gmail.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mlevitsk@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xu910121@sina.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.