Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760977AbYAJTzd (ORCPT ); Thu, 10 Jan 2008 14:55:33 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756105AbYAJTzS (ORCPT ); Thu, 10 Jan 2008 14:55:18 -0500 Received: from mx1.redhat.com ([66.187.233.31]:47351 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755108AbYAJTzQ (ORCPT ); Thu, 10 Jan 2008 14:55:16 -0500 Message-ID: <4786780F.90302@redhat.com> Date: Thu, 10 Jan 2008 14:54:55 -0500 From: Chuck Ebbert Organization: Red Hat User-Agent: Thunderbird 1.5.0.12 (X11/20071019) MIME-Version: 1.0 To: Arjan van de Ven CC: linux-kernel@vger.kernel.org, mingo@elte.hu Subject: Re: x86: Add the "print code before the trapping instruction" feature to 64 bit References: <20080110084739.5ba72522@laptopd505.fenrus.org> In-Reply-To: <20080110084739.5ba72522@laptopd505.fenrus.org> Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1057 Lines: 23 On 01/10/2008 11:47 AM, Arjan van de Ven wrote: > Subject: x86: Add the "print code before the trapping instruction" feature to 64 bit > From: Arjan van de Ven > > The 32 bit x86 tree has a very useful feature that prints the Code: line > for the code even before the trapping instrution (and the start of the > trapping instruction is then denoted with a <>). Unfortunately, the 64 bit > x86 tree does not yet have this feature, making diagnosing backtraces harder > than needed. > > This patch adds this feature in the same was as the 32 bit tree has > (including the same kernel boot parameter), and including a bugfix > to make the code use probe_kernel_address() rarther than a buggy (deadlocking) > __get_user. > If this get accepted I can stop ignoring x86_64 oops reports... -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/