Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755635AbYBED2u (ORCPT ); Mon, 4 Feb 2008 22:28:50 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754229AbYBED2j (ORCPT ); Mon, 4 Feb 2008 22:28:39 -0500 Received: from smtp2.linux-foundation.org ([207.189.120.14]:57988 "EHLO smtp2.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752796AbYBED2M (ORCPT ); Mon, 4 Feb 2008 22:28:12 -0500 Date: Mon, 4 Feb 2008 19:27:53 -0800 (PST) From: Linus Torvalds To: Maxim Levitsky cc: Ingo Molnar , linux-kernel@vger.kernel.org, Andrew Morton , Thomas Gleixner , "H. Peter Anvin" Subject: Re: [git pull] x86 arch updates for v2.6.25 In-Reply-To: <200802050436.31070.maximlevitsky@gmail.com> Message-ID: References: <20080130011550.GA31853@elte.hu> <200802050436.31070.maximlevitsky@gmail.com> User-Agent: Alpine 1.00 (LFD 882 2007-12-20) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1503 Lines: 35 On Tue, 5 Feb 2008, Maxim Levitsky wrote: > > The x86 tree was merged several times, but I don't see kgdb included in > latest mainline -git. > > So just one question, will it be included or no? I won't even consider pulling it unless it's offered as a separate tree, not mixed up with other things. At that point I can give a look. That said, I explained to Ingo why I'm not particularly interested in it. I don't think that "developer-centric" debugging is really even remotely our problem, and that I'm personally a lot more interested in infrastructure that helps normal users give better bug-reports. And kgdb isn't even _remotely_ it. So I'd merge a patch that puts oops information (or the whole console printout) in the Intel management stuff in a heartbeat. That code is likely much grottier than any kgdb thing will ever be (Intel really screwed up the interface and made it some insane XML thing), but it's also fundamentally more important - if it means that normal users can give oops reports after they happened in X (or, these days, probably more commonly during suspend/resume) and the machine just died. kgdb? Not so interesting. We have many more hard problems happening at user sites, not in developer hands. Linus -- 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/