From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (ozlabs.org [IPv6:2401:3900:2:1::2]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 41bbFS09zyzDqnG for ; Thu, 26 Jul 2018 12:11:56 +1000 (AEST) Message-ID: Subject: Re: [PATCH 0/7] powerpc: Modernize unhandled signals message From: Michael Neuling To: Murilo Opsfelder Araujo Cc: linux-kernel@vger.kernel.org, Alastair D'Silva , Andrew Donnellan , Balbir Singh , Benjamin Herrenschmidt , Christophe Leroy , Cyril Bur , "Eric W . Biederman" , Michael Ellerman , Nicholas Piggin , Paul Mackerras , Simon Guo , Sukadev Bhattiprolu , "Tobin C . Harding" , linuxppc-dev@lists.ozlabs.org Date: Thu, 26 Jul 2018 12:11:49 +1000 In-Reply-To: <20180725193647.GA23643@kermit-br-ibm-com> References: <20180724192720.32417-1-muriloo@linux.ibm.com> <0f185351330a7f1d66409fe6a2dc02aae6826039.camel@neuling.org> <20180725193647.GA23643@kermit-br-ibm-com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , > > Should we prefix every line with the PID to avoid this? >=20 > That's possible. An alternative would be prefixing each line with the > process name and its PID, as in the first line. For example: >=20 > pandafault[10758]: segfault (11) at 00000000100007d0 nip 000000001000= 061c lr 00007fffabc85100 code 2 in pandafault[10000000+10000] > pandafault[10758]: Instruction dump: > pandafault[10758]: 4bfffeec 4bfffee8 3c401002 38427f00 fbe1fff8 f821f= fc1 7c3f0b78 3d22fffe > pandafault[10758]: 392988d0 f93f0020 e93f0020 39400048 <99490000> 392= 00000 7d234b78 383f0040 >=20 > The above can be interleaved with other messages and we'll still be able > to match process and its corresponding instruction dump. LGTM. Thanks! Mikey