Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932077AbWHGNWW (ORCPT ); Mon, 7 Aug 2006 09:22:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932087AbWHGNWW (ORCPT ); Mon, 7 Aug 2006 09:22:22 -0400 Received: from public.id2-vpn.continvity.gns.novell.com ([195.33.99.129]:21302 "EHLO emea1-mh.id2.novell.com") by vger.kernel.org with ESMTP id S932077AbWHGNWV (ORCPT ); Mon, 7 Aug 2006 09:22:21 -0400 Message-Id: <44D75ACE.76E4.0078.0@novell.com> X-Mailer: Novell GroupWise Internet Agent 7.0.1 Date: Mon, 07 Aug 2006 14:22:54 +0100 From: "Jan Beulich" To: , "Andrew Morton" , "Andreas Kleen" Cc: Subject: notify_page_fault_chain Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 814 Lines: 15 All, I just noticed this addition to i386 and x86-64, conditionalized upon CONFIG_KPROBES. May I ask what the motivation for this compatibility breaking change is? Only performance? I consider it already questionable to split out a specific fault from the general die notification (previous users of the functionality all of the sudden won't get notifications for one of the most crucial faults anymore), but entirely hiding the functionality (unavailable without CONFIG_KPROBES, and even with it not getting exported) is really odd. Thanks for any clarification, Jan - 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/