From: Marcelo Tosatti <mtosatti@redhat.com>
To: Eric B Munson <emunson@mgebm.net>
Cc: kvm@vger.kernel.org, kvm-ia64@vger.kernel.org,
kvm-ppc@vger.kernel.org, avi@redhat.com, riel@redhat.com,
glommer@redhat.com, linux-kernel@vger.kernel.org,
aliguori@us.ibm.com, raharper@us.ibm.com
Subject: Re: [RFC PATCH 0/3] Avoid soft lockup message when KVM is stopped by host
Date: Thu, 4 Aug 2011 13:29:02 -0300 [thread overview]
Message-ID: <20110804162902.GA27692@amt.cnet> (raw)
In-Reply-To: <1312381501-27746-1-git-send-email-emunson@mgebm.net>
On Wed, Aug 03, 2011 at 10:24:58AM -0400, Eric B Munson wrote:
> This set is just a rough first pass at avoiding soft lockup warnings when a host
> pauses the execution of a guest. A flag is set by the host in the shared page
> used for the pvclock when the host goes to stop the guest. When the guest
> resumes and detects a soft lockup, this flag is checked and cleared and the soft
> lockup message is skipped.
>
> This currently breaks the build for non-x86 architectures but part of what I am
> looking for here is how to go about adding the function stubs for everything
> else.
To fix this, you can save/restore the offset added to kvmclock on
vmstop/vmstart. See hw/kvmclock.c in the qemu source tree.
prev parent reply other threads:[~2011-08-04 16:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 14:24 [RFC PATCH 0/3] Avoid soft lockup message when KVM is stopped by host Eric B Munson
2011-08-03 14:24 ` [RFC PATCH 1/3] Add flag to indicate that a vm was stopped by the host Eric B Munson
2011-08-03 14:25 ` [RFC PATCH 2/3] Add functions to check if the host has stopped the vm Eric B Munson
2011-08-03 14:25 ` [RFC PATCH 3/3] Add check for suspended vm in softlockup detector Eric B Munson
2011-08-04 8:37 ` [RFC PATCH 0/3] Avoid soft lockup message when KVM is stopped by host Dor Laor
2011-08-04 18:46 ` Anthony Liguori
2011-08-04 16:29 ` Marcelo Tosatti [this message]
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=20110804162902.GA27692@amt.cnet \
--to=mtosatti@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=emunson@mgebm.net \
--cc=glommer@redhat.com \
--cc=kvm-ia64@vger.kernel.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raharper@us.ibm.com \
--cc=riel@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox