From: Sean Christopherson <seanjc@google.com>
To: Liam Ni <liamni-oc@zhaoxin.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org, pbonzini@redhat.com, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
hpa@zytor.com, LiamNi@zhaoxin.com, CobeChen@zhaoxin.com,
LouisQi@zhaoxin.com, EwanHai@zhaoxin.com, FrankZhu@zhaoxin.com
Subject: Re: [PATCH] KVM: x86:Cancel hrtimer in the process of saving PIT state to reduce the performance overhead caused by hrtimer during guest stop.
Date: Mon, 17 Mar 2025 06:38:45 -0700 [thread overview]
Message-ID: <Z9gl5dbTfZsUCJy-@google.com> (raw)
In-Reply-To: <20250317091917.72477-1-liamni-oc@zhaoxin.com>
On Mon, Mar 17, 2025, Liam Ni wrote:
> When using the dump-guest-memory command in QEMU to dump
> the virtual machine's memory,the virtual machine will be
> paused for a period of time.If the guest (i.e., UEFI) uses
> the PIT as the system clock,it will be observed that the
> HRTIMER used by the PIT continues to run during the guest
> stop process, imposing an additional burden on the system.
> Moreover, during the guest restart process,the previously
> established HRTIMER will be canceled,and the accumulated
> timer events will be flushed.However, before the old
> HRTIMER is canceled,the accumulated timer events
> will "surreptitiously" inject interrupts into the guest.
>
> SO during the process of saving the KVM PIT state,
> the HRTIMER need to be canceled to reduce the performance overhead
> caused by HRTIMER during the guest stop process.
>
> i.e. if guest
>
> Signed-off-by: Liam Ni <liamni-oc@zhaoxin.com>
> ---
> arch/x86/kvm/x86.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index 045c61cc7e54..75355b315aca 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -6405,6 +6405,8 @@ static int kvm_vm_ioctl_get_pit(struct kvm *kvm, struct kvm_pit_state *ps)
>
> mutex_lock(&kps->lock);
> memcpy(ps, &kps->channels, sizeof(*ps));
> + hrtimer_cancel(&kvm->arch.vpit->pit_state.timer);
> + kthread_flush_work(&kvm->arch.vpit->expired);
KVM cannot assume userspace wants to stop the PIT when grabbing a snapshot. It's
a significant ABI change, and not desirable in all cases.
> mutex_unlock(&kps->lock);
> return 0;
> }
> @@ -6428,6 +6430,8 @@ static int kvm_vm_ioctl_get_pit2(struct kvm *kvm, struct kvm_pit_state2 *ps)
> memcpy(ps->channels, &kvm->arch.vpit->pit_state.channels,
> sizeof(ps->channels));
> ps->flags = kvm->arch.vpit->pit_state.flags;
> + hrtimer_cancel(&kvm->arch.vpit->pit_state.timer);
> + kthread_flush_work(&kvm->arch.vpit->expired);
> mutex_unlock(&kvm->arch.vpit->pit_state.lock);
> memset(&ps->reserved, 0, sizeof(ps->reserved));
> return 0;
> --
> 2.25.1
>
next prev parent reply other threads:[~2025-03-17 13:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 9:19 [PATCH] KVM: x86:Cancel hrtimer in the process of saving PIT state to reduce the performance overhead caused by hrtimer during guest stop Liam Ni
2025-03-17 13:38 ` Sean Christopherson [this message]
2025-03-25 6:10 ` LiamNioc
2025-04-04 14:48 ` Sean Christopherson
2025-04-07 2:19 ` LiamNioc
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=Z9gl5dbTfZsUCJy-@google.com \
--to=seanjc@google.com \
--cc=CobeChen@zhaoxin.com \
--cc=EwanHai@zhaoxin.com \
--cc=FrankZhu@zhaoxin.com \
--cc=LiamNi@zhaoxin.com \
--cc=LouisQi@zhaoxin.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=liamni-oc@zhaoxin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.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