From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40829) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V1XRC-0007Iy-Oh for qemu-devel@nongnu.org; Tue, 23 Jul 2013 03:55:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V1XRA-0005RD-NH for qemu-devel@nongnu.org; Tue, 23 Jul 2013 03:55:14 -0400 Received: from e06smtp16.uk.ibm.com ([195.75.94.112]:60036) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V1XRA-0005QL-Bs for qemu-devel@nongnu.org; Tue, 23 Jul 2013 03:55:12 -0400 Received: from /spool/local by e06smtp16.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 23 Jul 2013 08:49:15 +0100 Received: from b06cxnps3075.portsmouth.uk.ibm.com (d06relay10.portsmouth.uk.ibm.com [9.149.109.195]) by d06dlp02.portsmouth.uk.ibm.com (Postfix) with ESMTP id 601F5219005F for ; Tue, 23 Jul 2013 08:59:15 +0100 (BST) Received: from d06av03.portsmouth.uk.ibm.com (d06av03.portsmouth.uk.ibm.com [9.149.37.213]) by b06cxnps3075.portsmouth.uk.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r6N7suf463897852 for ; Tue, 23 Jul 2013 07:54:56 GMT Received: from d06av03.portsmouth.uk.ibm.com (localhost [127.0.0.1]) by d06av03.portsmouth.uk.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id r6N7t7Eb025089 for ; Tue, 23 Jul 2013 01:55:07 -0600 Message-ID: <51EE36DA.6060800@de.ibm.com> Date: Tue, 23 Jul 2013 09:55:06 +0200 From: Christian Borntraeger MIME-Version: 1.0 References: <87li4xrdig.fsf@elfo.elfo> In-Reply-To: <87li4xrdig.fsf@elfo.elfo> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] KVM call agenda for 2013-07-30 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: quintela@redhat.com Cc: qemu-devel qemu-devel , KVM devel mailing list On 23/07/13 08:33, Juan Quintela wrote: > > Hi > > Please, send any topic that you are interested in covering. - soft reset and other reset variants. What is the right way to go? (e.g. on s390 there are several reset variants that reset a defined subset of the system. This can be triggered by operating systems, e.g. kdump uses a diagnose instruction that resets the device subsystem and parts of the cpu registers (some are unchanged, this allows to take a proper crash dump with a well defined system state)