Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fast tracepoints
Date: Tue, 05 Jan 2010 20:07:00 -0000	[thread overview]
Message-ID: <83d41oco6k.fsf@gnu.org> (raw)
In-Reply-To: <4B42A628.5060302@codesourcery.com>

> Date: Mon, 04 Jan 2010 18:38:32 -0800
> From: Stan Shebs <stan@codesourcery.com>
> 
> This patch adds "fast" tracepoints to GDB.

Thanks.

> Index: NEWS
> ===================================================================
> RCS file: /cvs/src/src/gdb/NEWS,v
> retrieving revision 1.344
> diff -p -r1.344 NEWS
> *** NEWS	31 Dec 2009 17:47:42 -0000	1.344
> --- NEWS	5 Jan 2010 02:13:28 -0000

This part is OK, but please give me 2 spaces between sentences.

> *** doc/gdb.texinfo	1 Jan 2010 07:54:37 -0000	1.654
> --- doc/gdb.texinfo	5 Jan 2010 02:13:29 -0000

A few comments for this part:

> + Some targets may support @dfn{fast tracepoints}, which are inserted in
> + a different way (such as with a jump instead of a trap), that is
> + faster but possibly restricted in where they may be installed.

Please put the "@cindex fast tracepoints" entry here, not 50 lines
below.

> + The @code{ftrace} command sets a fast tracepoint.  For targets that
> + support it, fast tracepoints will use a more efficient but possibly

"For targets that support them, fast tracepoints will use ..."

Okay with those changes.


  reply	other threads:[~2010-01-05 20:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-05  2:38 Stan Shebs
2010-01-05 20:07 ` Eli Zaretskii [this message]
2010-01-05 22:43 ` Tom Tromey
2010-01-06  0:55   ` Stan Shebs
2010-01-06  9:39     ` Mark Wielaard
2010-01-06 23:09     ` Tom Tromey
2010-01-06 23:41       ` Stan Shebs

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=83d41oco6k.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=stan@codesourcery.com \
    /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