mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Thompson <daniel.thompson@linaro.org>
To: Li Qiang <liq3ea@gmail.com>,
	jason.wessel@windriver.com, corbet@lwn.net, labbott@redhat.com
Cc: 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 16:28:38 +0100	[thread overview]
Message-ID: <bc97a972-7eb6-c528-d7b4-d6daa793e29b@linaro.org> (raw)
In-Reply-To: <1492567125-61756-1-git-send-email-liqiang6-s@360.cn>

On 19/04/17 02:58, Li Qiang wrote:
> CONFIG_STRICT_KERNEL_RWX is no longer selectable on most architectures.
> Update this info to thedocumentation.

"git grep STRICT_KERNEL_RWX" comes up with nothing.

It is selectable on any architecture? If not we should remove it entirely!


Daniel.


>
> 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'.
>      </para>
>      <para>
>      Next you should choose one of more I/O drivers to interconnect
>

  reply	other threads:[~2017-04-20 15:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-19  1:58 Li Qiang
2017-04-20 15:28 ` Daniel Thompson [this message]
     [not found]   ` <CAKXe6S+gu2xm+rC390_PTt5EoGgG8psCJD11333_7ndz6TZHAg@mail.gmail.com>
2017-04-21  9:19     ` Daniel Thompson
2017-04-20 21:09 ` Jonathan Corbet

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=bc97a972-7eb6-c528-d7b4-d6daa793e29b@linaro.org \
    --to=daniel.thompson@linaro.org \
    --cc=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

all inboxes | Powered by JetHome®