[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4EE9E023.4000904@redhat.com>
Date: Thu, 15 Dec 2011 13:55:15 +0200
From: Avi Kivity <avi@...hat.com>
To: Amit Shah <amit.shah@...hat.com>
CC: Eric B Munson <emunson@...bm.net>, mingo@...hat.com, hpa@...or.com,
arnd@...db.de, ryanh@...ux.vnet.ibm.com, aliguori@...ibm.com,
mtosatti@...hat.com, jeremy.fitzhardinge@...rix.com,
levinsasha928@...il.com, Jan Kiszka <jan.kiszka@...mens.com>,
kvm@...r.kernel.org, linux-arch@...r.kernel.org, x86@...nel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/5 V5] Avoid soft lockup message when KVM is stopped
by host
On 12/08/2011 01:34 PM, Amit Shah wrote:
> On (Mon) 05 Dec 2011 [15:18:59], Eric B Munson wrote:
> > When a guest kernel is stopped by the host hypervisor it can look like a soft
> > lockup to the guest kernel. This false warning can mask later soft lockup
> > warnings which may be real. This patch series adds a method for a host
> > hypervisor to communicate to a guest kernel that it is being stopped. The
> > final patch in the series has the watchdog check this flag when it goes to
> > issue a soft lockup warning and skip the warning if the guest knows it was
> > stopped.
>
> Guest S4 would need similar treatment, and I think the code in the two
> approaches can be shared. Just something to consider.
>
Why does S4 need any treatment? The guest is aware that it's sleeping,
unlike the other cases treated here.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists