From: Dave Martin <dave.martin@linaro.org>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
Russell King <linux@arm.linux.org.uk>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: Document ARM's user_debug parameter
Date: Tue, 26 Jul 2011 09:57:25 +0100 [thread overview]
Message-ID: <20110726085721.GB2075@arm.com> (raw)
In-Reply-To: <20110725142924.85de25dd.rdunlap@xenotime.net>
On Mon, Jul 25, 2011 at 02:29:24PM -0700, Randy Dunlap wrote:
> 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
linux$ git grep UDBG_SYSCALL -- arch/arm/
include/asm/system.h:#define UDBG_SYSCALL (1 << 1)
kernel/traps.c: if (user_debug & UDBG_SYSCALL) {
kernel/traps.c: if (user_debug & UDBG_SYSCALL) {
Looking at kernel/traps.c, it looks like only undefined or obsolete
syscalls are logged. It could be worth clarifying this in the wording,
both here and in arch/arm/Kconfig.debug.
Cheers
---Dave
> > + 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 ***
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2011-07-26 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-25 1:15 [PATCH] Documentation: Document ARM's user_debug parameter Stephen Boyd
2011-07-25 21:29 ` Randy Dunlap
2011-07-26 8:57 ` Dave Martin [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=20110726085721.GB2075@arm.com \
--to=dave.martin@linaro.org \
--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=rdunlap@xenotime.net \
--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