From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HsiDT-0007gI-TN
	for qemu-devel@nongnu.org; Mon, 28 May 2007 12:37:07 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HsiDR-0007g6-ID
	for qemu-devel@nongnu.org; Mon, 28 May 2007 12:37:06 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HsiDR-0007g3-D1
	for qemu-devel@nongnu.org; Mon, 28 May 2007 12:37:05 -0400
Received: from mail.gmx.net ([213.165.64.20])
	by monty-python.gnu.org with smtp (Exim 4.60)
	(envelope-from <clemens.kol@gmx.at>) id 1HsiDQ-0003Pm-RL
	for qemu-devel@nongnu.org; Mon, 28 May 2007 12:37:05 -0400
Message-ID: <465B052E.2070303@gmx.at>
Date: Mon, 28 May 2007 18:37:02 +0200
From: Clemens Kolbitsch <clemens.kol@gmx.at>
MIME-Version: 1.0
Subject: Re: RE: [Qemu-devel] QEMU/PCI shutdown event
References: <20070528160302.540gmx1@mx058.gmx.net>
In-Reply-To: <20070528160302.540gmx1@mx058.gmx.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org


>> hi everyone!
>> i'm programming a pci-device that includes some threads &
>> socket-connections (that allow remote debugging of my device).
>>
>> however, i want to cleanly shutdown all threads and sockets when qemu
>> exits... is there an easy way of getting informed of a qemu shutdown?
>>
>> (something similar to pci_device_init...)
>>
>> thanks!!
>>
>>     
>
> You can use qemu_register_reset handler.
> Note that it get's called when the guests exits but not if you just quit
> the monitor.
>   
hm... since i'm really tearing down qemu quite often (sigint) that's not 
really a solutions for me, but thanks!! If nothing else works, i'll give 
it a try :-)

any other ideas?