mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
	Russell King <linux@arm.linux.org.uk>
Subject: Re: [PATCH] Documentation: Document ARM's user_debug parameter
Date: Mon, 25 Jul 2011 14:29:24 -0700	[thread overview]
Message-ID: <20110725142924.85de25dd.rdunlap@xenotime.net> (raw)
In-Reply-To: <1311556514-24728-1-git-send-email-sboyd@codeaurora.org>

On Sun, 24 Jul 2011 18:15:14 -0700 Stephen Boyd wrote:

> Usually kernel parameters are documented in kernel-parameters.txt
> but user_debug is only documented in the Kconfig. Document the
> option and point to the Kconfig help text for more info.
> 
> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
> Cc: Russell King <linux@arm.linux.org.uk>

Is this a superset of 'print_fatal_signals'?

Applied, thanks.

> ---
>  Documentation/kernel-parameters.txt |   10 ++++++++++
>  1 files changed, 10 insertions(+), 0 deletions(-)
> 
> diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
> index aa47be7..8186adc 100644
> --- a/Documentation/kernel-parameters.txt
> +++ b/Documentation/kernel-parameters.txt
> @@ -2612,6 +2612,16 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
>  					medium is write-protected).
>  			Example: quirks=0419:aaf5:rl,0421:0433:rc
>  
> +	user_debug=	[KNL,ARM]
> +			Format: <int>
> +			See arch/arm/Kconfig.debug help text.
> +				 1 - undefined instruction events
> +				 2 - system calls
> +				 4 - invalid data aborts
> +				 8 - SIGSEGV faults
> +				16 - SIGBUS faults
> +			Example: user_debug=31
> +
>  	userpte=
>  			[X86] Flags controlling user PTE allocations.
>  
> -- 
> Sent by an employee of the Qualcomm Innovation Center, Inc.
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2011-07-25 21:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-25  1:15 Stephen Boyd
2011-07-25 21:29 ` Randy Dunlap [this message]
2011-07-26  8:57   ` Dave Martin

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=20110725142924.85de25dd.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=sboyd@codeaurora.org \
    /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®