From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Borntraeger Subject: Re: KVM call agenda for 2013-07-30 Date: Tue, 23 Jul 2013 09:55:06 +0200 Message-ID: <51EE36DA.6060800@de.ibm.com> References: <87li4xrdig.fsf@elfo.elfo> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: qemu-devel qemu-devel , KVM devel mailing list To: quintela@redhat.com Return-path: In-Reply-To: <87li4xrdig.fsf@elfo.elfo> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org List-Id: kvm.vger.kernel.org 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)