Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754869AbbHJRXO (ORCPT ); Mon, 10 Aug 2015 13:23:14 -0400 Received: from mail.windriver.com ([147.11.1.11]:36468 "EHLO mail.windriver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753472AbbHJRXJ (ORCPT ); Mon, 10 Aug 2015 13:23:09 -0400 Message-ID: <55C8DDEA.8070508@windriver.com> Date: Mon, 10 Aug 2015 12:22:50 -0500 From: Jason Wessel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.8.0 MIME-Version: 1.0 To: Paul Gortmaker , CC: Arnd Bergmann , Greg Kroah-Hartman , Subject: Re: [PATCH 4/4] drivers/misc: make kgdbts.c slightly more explicitly non-modular References: <1439066105-18412-1-git-send-email-paul.gortmaker@windriver.com> <1439066105-18412-5-git-send-email-paul.gortmaker@windriver.com> In-Reply-To: <1439066105-18412-5-git-send-email-paul.gortmaker@windriver.com> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1817 Lines: 34 On 08/08/2015 03:35 PM, Paul Gortmaker wrote: > The Kconfig currently controlling compilation of this code is: > > lib/Kconfig.kgdb:config KGDB_TESTS > lib/Kconfig.kgdb: bool "KGDB: internal test suite" > > ...meaning that it currently is not being built as a module by anyone. > > Lets remove the modular code that is essentially orphaned, so that > when reading the driver there is no doubt it is builtin-only. > > Since module_init translates to device_initcall in the non-modular > case, the init ordering remains unchanged with this commit. > > We also delete the MODULE_LICENSE tag etc. since all that information > is already contained at the top of the file in the comments. > > We can't remove the module.h include since we've kept the use of > module_param in this file for now. This is correct, if you remove that there is no way to invoke the test suite later on at run time. I tried out the patch and it works fine with no regressions. Unrelated to this it seems there is a problem with the read/write of the break points when crossing the point where the kernel write protects the read-only data. Basically, the break point is implanted into the code page, which is made read-only, and then it can no longer be removed. What we typically do in that case "after read-only pages are established", is to use COW pages for the break points. I'll have to look further into what if anything we might have to do about it. At least the emergency printk logic worked to show there is a problem. :-) Acked-by: Jason Wessel -- 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/