From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH] lapic3: kvm: qemu: fix a possible deadlock situation in save/restore Date: Tue, 07 Aug 2007 11:31:06 +0300 Message-ID: <46B82DCA.8000601@qumranet.com> References: <37E52D09333DE2469A03574C88DBF40FA9C1A4@pdsmsx414.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel To: "He, Qing" Return-path: In-Reply-To: <37E52D09333DE2469A03574C88DBF40FA9C1A4-wq7ZOvIWXbM/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org He, Qing wrote: > kvm: qemu: fix a possible deadlock situation in save/restore > > If a VM using userspace irqchip is saved when it's in HLT state, > and is restored to use the in-kernel irqchip, the HLT state flag > is also restored. This HLT flag in userspace HLT handling prevents > kvm kernel driver from being run. And at the same time, the original > userspace irqchip is now unused thus will not generate any interrupt > to wake up the HLT state. This patch fixes this deadlock situation > by dropping the HLT state at restore time > > Applied, thanks. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/