From: Sean Christopherson <seanjc@google.com>
To: Suleiman Souhlal <suleiman@google.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, "H. Peter Anvin" <hpa@zytor.com>,
Chao Gao <chao.gao@intel.com>,
David Woodhouse <dwmw2@infradead.org>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
ssouhlal@freebsd.org
Subject: Re: [PATCH v3 1/3] kvm: Introduce kvm_total_suspend_ns().
Date: Tue, 7 Jan 2025 07:27:25 -0800 [thread overview]
Message-ID: <Z31H3dkAktjUO2tR@google.com> (raw)
In-Reply-To: <20250107042202.2554063-2-suleiman@google.com>
KVM: for the scope.
On Tue, Jan 07, 2025, Suleiman Souhlal wrote:
> It returns the cumulative nanoseconds that the host has been suspended.
Please write changelogs that are standalone. "It returns ..." is completely
nonsensical without the context of the shortlog.
> It is intended to be used for reporting host suspend time to the guest.
>
> Change-Id: I8f644c9fbdb2c48d2c99dd9efaa5c85a83a14c2a
Drop gerrit's metadata before posting.
> Signed-off-by: Suleiman Souhlal <suleiman@google.com>
> ---
> include/linux/kvm_host.h | 2 ++
> virt/kvm/kvm_main.c | 26 ++++++++++++++++++++++++++
> 2 files changed, 28 insertions(+)
>
> diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
> index 401439bb21e3e6..cf926168b30820 100644
> --- a/include/linux/kvm_host.h
> +++ b/include/linux/kvm_host.h
> @@ -2553,4 +2553,6 @@ long kvm_arch_vcpu_pre_fault_memory(struct kvm_vcpu *vcpu,
> struct kvm_pre_fault_memory *range);
> #endif
>
> +u64 kvm_total_suspend_ns(void);
> +
> #endif
> diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
> index de2c11dae23163..d5ae237df76d0d 100644
> --- a/virt/kvm/kvm_main.c
> +++ b/virt/kvm/kvm_main.c
> @@ -889,13 +889,39 @@ static int kvm_init_mmu_notifier(struct kvm *kvm)
>
> #endif /* CONFIG_KVM_GENERIC_MMU_NOTIFIER */
>
> +static u64 last_suspend;
> +static u64 total_suspend_ns;
> +
> +u64 kvm_total_suspend_ns(void)
> +{
> + return total_suspend_ns;
> +}
> +
> +
Extra whitespace.
> #ifdef CONFIG_HAVE_KVM_PM_NOTIFIER
> +static int kvm_pm_notifier(struct kvm *kvm, unsigned long state)
> +{
> + switch (state) {
> + case PM_HIBERNATION_PREPARE:
> + case PM_SUSPEND_PREPARE:
> + last_suspend = ktime_get_boottime_ns();
> + case PM_POST_HIBERNATION:
> + case PM_POST_SUSPEND:
> + total_suspend_ns += ktime_get_boottime_ns() - last_suspend;
This is broken. As should be quite clear from the function parameters, this is
a per-VM notifier. While clobbering "last_suspend" is relatively benign,
accumulating into "total_suspend_ns" for every VM will cause the "total" suspend
time to be wildly inaccurate if there are multiple VMs.
> + }
> +
> + return NOTIFY_DONE;
> +}
> +
> static int kvm_pm_notifier_call(struct notifier_block *bl,
> unsigned long state,
> void *unused)
> {
> struct kvm *kvm = container_of(bl, struct kvm, pm_notifier);
>
> + if (kvm_pm_notifier(kvm, state) != NOTIFY_DONE)
> + return NOTIFY_BAD;
This is ridiculous on multiple fronts. There's zero reason for kvm_pm_notifier()
to return a value, it always succeeds. I also see zero reason to put this code
in common KVM. It's 100% an x86-only concept, and x86 is the only architecture
that implements kvm_arch_pm_notifier(). So just shove the logic into x86's
implementation.
> +
> return kvm_arch_pm_notifier(kvm, state);
> }
>
> --
> 2.47.1.613.gc27f4b7a9f-goog
>
next prev parent reply other threads:[~2025-01-07 15:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 4:21 [PATCH v3 0/3] KVM: x86: Include host suspended time in steal time Suleiman Souhlal
2025-01-07 4:21 ` [PATCH v3 1/3] kvm: Introduce kvm_total_suspend_ns() Suleiman Souhlal
2025-01-07 15:27 ` Sean Christopherson [this message]
2025-01-07 16:43 ` Suleiman Souhlal
2025-01-08 7:15 ` kernel test robot
2025-01-08 8:36 ` kernel test robot
2025-01-15 21:49 ` Sean Christopherson
2025-01-17 6:35 ` Suleiman Souhlal
2025-01-17 16:52 ` Sean Christopherson
2025-01-21 5:37 ` Suleiman Souhlal
2025-01-21 20:22 ` Sean Christopherson
2025-02-04 7:58 ` Suleiman Souhlal
2025-02-05 5:55 ` Suleiman Souhlal
2025-02-06 1:29 ` Sean Christopherson
2025-02-13 3:56 ` Suleiman Souhlal
2025-01-07 4:22 ` [PATCH v3 2/3] KVM: x86: Include host suspended time in steal time Suleiman Souhlal
2025-01-07 15:37 ` Sean Christopherson
2025-01-08 4:05 ` Suleiman Souhlal
2025-01-08 15:17 ` Sean Christopherson
2025-01-07 4:22 ` [PATCH v3 3/3] KVM: x86: Document host suspend being included " Suleiman Souhlal
2025-01-07 15:37 ` Sean Christopherson
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=Z31H3dkAktjUO2tR@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=chao.gao@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=ssouhlal@freebsd.org \
--cc=suleiman@google.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