From: Jonathan Corbet <corbet@lwn.net>
To: Li Qiang <liq3ea@gmail.com>
Cc: jason.wessel@windriver.com, labbott@redhat.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
kgdb-bugreport@lists.sourceforge.net,
Li Qiang <liqiang6-s@360.cn>
Subject: Re: [PATCH] Documentation: DocBook: kgdb: update CONFIG_STRICT_KERNEL_RWX info
Date: Thu, 20 Apr 2017 15:09:14 -0600 [thread overview]
Message-ID: <20170420150914.18399eb8@lwn.net> (raw)
In-Reply-To: <1492567125-61756-1-git-send-email-liqiang6-s@360.cn>
On Tue, 18 Apr 2017 18:58:45 -0700
Li Qiang <liq3ea@gmail.com> wrote:
> CONFIG_STRICT_KERNEL_RWX is no longer selectable on most architectures.
> Update this info to the documentation.
>
> Signed-off-by: Li Qiang <liqiang6-s@360.cn>
> ---
> Documentation/DocBook/kgdb.tmpl | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/DocBook/kgdb.tmpl b/Documentation/DocBook/kgdb.tmpl
> index 856ac20..ef0b67b 100644
> --- a/Documentation/DocBook/kgdb.tmpl
> +++ b/Documentation/DocBook/kgdb.tmpl
> @@ -121,7 +121,9 @@
> If kgdb supports it for the architecture you are using, you can
> use hardware breakpoints if you desire to run with the
> CONFIG_STRICT_KERNEL_RWX option turned on, else you need to turn off
> - this option.
> + this option. In most architectures, this option is not selectable.
> + For this situation, it can be turned off by adding a runtime parameter
> + 'rodata=off'.
So this is an improvement, I guess, though the paragraph remains kind of
confusing. Is there any chance we could actually just say which
architectures can use hardware breakpoints, and which should boot with
rodata=off?
Thanks,
jon
prev parent reply other threads:[~2017-04-20 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 1:58 [PATCH] Documentation: DocBook: kgdb: update CONFIG_STRICT_KERNEL_RWX info Li Qiang
2017-04-20 15:28 ` Daniel Thompson
[not found] ` <CAKXe6S+gu2xm+rC390_PTt5EoGgG8psCJD11333_7ndz6TZHAg@mail.gmail.com>
2017-04-21 9:19 ` Daniel Thompson
2017-04-20 21:09 ` Jonathan Corbet [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=20170420150914.18399eb8@lwn.net \
--to=corbet@lwn.net \
--cc=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=labbott@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liq3ea@gmail.com \
--cc=liqiang6-s@360.cn \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox