From: Jason Wessel <jason.wessel@windriver.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>,
<linux-kernel@vger.kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<kgdb-bugreport@lists.sourceforge.net>
Subject: Re: [PATCH 4/4] drivers/misc: make kgdbts.c slightly more explicitly non-modular
Date: Mon, 10 Aug 2015 12:22:50 -0500 [thread overview]
Message-ID: <55C8DDEA.8070508@windriver.com> (raw)
In-Reply-To: <1439066105-18412-5-git-send-email-paul.gortmaker@windriver.com>
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 <jason.wessel@windriver.com>
prev parent reply other threads:[~2015-08-10 17:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-08 20:35 [PATCH 0/4] char/misc: make some drivers more explicitly non-modular Paul Gortmaker
2015-08-08 20:35 ` [PATCH 1/4] drivers/char: make efirtc.c driver " Paul Gortmaker
2015-08-08 20:35 ` [PATCH 2/4] drivers/char: make SGI snsc.c " Paul Gortmaker
2015-08-08 20:35 ` [PATCH 3/4] drivers/char: make hpet.c " Paul Gortmaker
2015-08-08 20:35 ` [PATCH 4/4] drivers/misc: make kgdbts.c slightly more " Paul Gortmaker
2015-08-10 17:22 ` Jason Wessel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55C8DDEA.8070508@windriver.com \
--to=jason.wessel@windriver.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.