From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48528) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X04Wj-00040Y-Pp for qemu-devel@nongnu.org; Thu, 26 Jun 2014 03:55:33 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1X04Wc-0005wJ-0B for qemu-devel@nongnu.org; Thu, 26 Jun 2014 03:55:25 -0400 Received: from e23smtp02.au.ibm.com ([202.81.31.144]:48653) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X04Wb-0005uo-7A for qemu-devel@nongnu.org; Thu, 26 Jun 2014 03:55:17 -0400 Received: from /spool/local by e23smtp02.au.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 26 Jun 2014 17:55:12 +1000 From: Nikunj A Dadhania In-Reply-To: <53AAB335.1070608@suse.de> References: <1402574971-26672-2-git-send-email-nikunj@linux.vnet.ibm.com> <53A006A9.90108@suse.de> <871tunc288.fsf@linux.vnet.ibm.com> <53A01006.6080800@suse.de> <87y4wvamb3.fsf@linux.vnet.ibm.com> <53A01220.90009@suse.de> <87vbrzale9.fsf@linux.vnet.ibm.com> <87a991ppv7.fsf@abhimanyu.in.ibm.com> <53AAAC97.6030409@suse.de> <87zjh1ns91.fsf@abhimanyu.in.ibm.com> <53AAB335.1070608@suse.de> Date: Thu, 26 Jun 2014 13:25:04 +0530 Message-ID: <87simsw1ev.fsf@abhimanyu.in.ibm.com> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Qemu-devel] [PATCH v2] ppc: spapr-rtas - implement os-term rtas call List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf , qemu-devel@nongnu.org, Anton Blanchard Cc: aik@au1.ibm.com, Benjamin Herrenschmidt , qemu-ppc@nongnu.org Alexander Graf writes: > On 25.06.14 13:27, Nikunj A Dadhania wrote: >> Alexander Graf writes: >> >> Let me put down my understanding: >> >> There are two possible way to handle kernel panic: >> 1) Kdump service running in guest - already working >> 2) Pass the kernel panic information to hypervisor - not there in Qemu >> pseries >> >> So without kdump service running, if linux kernel hits a panic, its going >> to check os-term and extended-os-term, only then its going to call >> os-term. > > It's checking both for a reason. Find that reason. Here is what I figured out from PAPR: rtas ibm,os-term, does not gaurantee a return back to the guest cpu. If ibm,extended-os-term property is set rtas call return will always occur. Regards Nikunj