From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Maxim Levitsky <mlevitsk@redhat.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Marc Zyngier <maz@kernel.org>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Suleiman Souhlal <suleiman@google.com>,
x86@kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv3 2/2] kvm: x86: implement KVM PM-notifier
Date: Tue, 8 Jun 2021 09:44:51 +0900 [thread overview]
Message-ID: <YL69g007MKqxiZG/@google.com> (raw)
In-Reply-To: <fe13fe734a01bb54f47fea06624c617beb062fdd.camel@redhat.com>
On (21/06/07 15:54), Maxim Levitsky wrote:
>
> Overall this looks OK to me.
>
> Do you have a test case in which this patch helps to make the guest behave better after
> the host suspend though? I tested this and I don't see any significant change.
> (guest works after host suspend before and after, and I still have clocksource
> watchdogs firing in the guest)
Yes, we have automated suspend-resume tests. What happens for us is that,
when not properly paused, guests, upon host resume, discover jiffies spikes
and trigger all sort of watchdogs.
next prev parent reply other threads:[~2021-06-08 0:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 2:10 [PATCHv3 1/2] kvm: add PM-notifier Sergey Senozhatsky
2021-06-06 2:10 ` [PATCHv3 2/2] kvm: x86: implement KVM PM-notifier Sergey Senozhatsky
2021-06-07 12:54 ` Maxim Levitsky
2021-06-08 0:44 ` Sergey Senozhatsky [this message]
2021-06-08 0:47 ` Sergey Senozhatsky
2021-06-10 12:15 ` Paolo Bonzini
2021-06-07 16:35 ` [PATCHv3 1/2] kvm: add PM-notifier Marc Zyngier
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=YL69g007MKqxiZG/@google.com \
--to=senozhatsky@chromium.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=mlevitsk@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=suleiman@google.com \
--cc=vkuznets@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).