linux-kernel - Re: [PATCH 0/5 V5] Avoid soft lockup message when KVM is stopped by host

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 14 Dec 2011 17:01:11 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Anthony Liguori <aliguori@...ibm.com>
CC:	Marcelo Tosatti <mtosatti@...hat.com>,
	Eric B Munson <emunson@...bm.net>, mingo@...hat.com,
	hpa@...or.com, arnd@...db.de, ryanh@...ux.vnet.ibm.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/14/2011 04:49 PM, Anthony Liguori wrote:
>>
>>> About SIGSTOP, that is a corner case. Unsure if its even properly
>>> supported
>>> by QEMU.
>>
>> It works from my experience.
>
>
> We don't adjust vm_clock's offset on SIGSTOP/SIGCONT so while it may
> appear to work okay, QEMU isn't exhibiting the behavior it is supposed
> to.

Should we trap and handle SIGCONT?

-- 
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/