public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco.com>
To: Markus Metzger <markus.t.metzger@intel.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, tglx@linutronix.de,
	markus.t.metzger@gmail.com
Subject: Re: [rfc] x86, bts: improve X86_PTRACE_BTS help text
Date: Wed, 15 Oct 2008 23:57:23 -0700	[thread overview]
Message-ID: <ada1vyhc9ik.fsf@cisco.com> (raw)
In-Reply-To: <20081015182902.A30726@sedona.ch.intel.com> (Markus Metzger's message of "Wed, 15 Oct 2008 18:29:02 +0200")

Thanks for improving the help text; it looks much better.

One comment:

 >  config X86_DS
 > -	bool "Debug Store support"
 > -	default y
 > -	help
 > -	  Add support for Debug Store.
 > -	  This allows the kernel to provide a memory buffer to the hardware
 > -	  to store various profiling and tracing events.
 > +	def_bool X86_PTRACE_BTS
 > +	depends on X86_DEBUGCTLMSR

using def_bool here to get this turned on if X86_PTRACE_BTS is set
doesn't seem scalable to more uses of X86_DS.  I would have thought that
having X86_PTRACE_BTS select X86_DS would make more sense.

Or are other users of X86_DS not planned?  In which case should there be
a separate X86_DS option at all?

 > +	  This adds a ptrace interface to the hardware's branch trace store.
 > +
 > +	  Debuggers may use it to collect an execution trace of the debugged
 > +	  application in order to answer the question 'how did I get here?'.
 > +	  Debuggers may trace user mode as well as kernel mode.
 > +
 > +	  Say Y unless there is no application development on this machine
 > +	  and you want to save a small amount of code size.

This looks much better -- someone like me could read this and make an
informed decision about the config option.

Thanks,
  Roland

  reply	other threads:[~2008-10-16  6:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-15 16:29 [rfc] x86, bts: improve X86_PTRACE_BTS help text Markus Metzger
2008-10-16  6:57 ` Roland Dreier [this message]
2008-10-16  7:12   ` Metzger, Markus T

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=ada1vyhc9ik.fsf@cisco.com \
    --to=rdreier@cisco.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus.t.metzger@gmail.com \
    --cc=markus.t.metzger@intel.com \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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