Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Walfred Tedeschi <walfred.tedeschi@intel.com>
Cc: tromey@redhat.com, mark.kettenis@xs4all.nl, gdb-patches@sourceware.org
Subject: Re: [PATCH V7 8/8] Add MPX feature description to GDB manual.
Date: Mon, 18 Nov 2013 20:26:00 -0000	[thread overview]
Message-ID: <528A6878.2090903@redhat.com> (raw)
In-Reply-To: <1381320034-4092-9-git-send-email-walfred.tedeschi@intel.com>

On 10/09/2013 01:00 PM, Walfred Tedeschi wrote:
> +The @samp{org.gnu.gdb.i386.mpx} is an optional feature representing Intel(R)
> +Memory Protection Extension (MPX).  MPX adds the bound registers @samp{BND0}
> +@footnote{Capital letters were used to distinguish between architecture
> +registers and pseudo registers.  

I'd suggest s/were/are.  (here and elsewhere)

> A set of pseudo register for the bound
> +registers were created to simplify the display.} through @samp{BND3}.  Bound
> +registers store a pair of 64-bit values which are the lower bound and upper
> +bound.  Bounds are effective addresses or memory locations.  The upper bounds
> +are architecturally represented in 1's complement form.  A bound having lower
> +bound = 0, and upper bound = 0 (1's complement of all bits set) will allow
> +access to the entire address space.
> +
> +In order to take the upper bound complement
> +of one into account the @samp{BND0} through @samp{BND3} are described in GDB
> +as @samp{bnd0raw} through @samp{bnd3raw}.  Pseudo registers @samp{bnd0} through
> +@samp{bnd3} display the upper bound performing the complement of one operation,
> +i.e.@ when upper bound in @samp{bnd0raw} is 0 in the GDB @samp{bnd0} it will be
> +@code{0xfff...}.  The feature adds the following registers:

This node is mostly meant for remote stub writers.
I'd suggest only describing here what's included in the description (the raw
registers), and describe the pseudo registers elsewhere where regular users will
look (making sure to word things in a user-friendly way, perhaps with examples.)

Perhaps in Architectures->i386  (x86 Architecture-specific Issues)?

> +
> +@itemize @minus
> +@item
> +@samp{bnd0raw} through @samp{bnd3raw} for i386, amd64 and x32.
> +@item
> +@samp{bndcfgu} and @samp{bndstatus} for i386, amd64 and x32.
> +@end itemize
> +
>  The @samp{org.gnu.gdb.i386.linux} feature is optional.  It should
>  describe a single register, @samp{orig_eax}.


-- 
Pedro Alves


  reply	other threads:[~2013-11-18 19:21 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-09 12:01 [PATCH V7 0/8] Intel(R) MPX register support Walfred Tedeschi
2013-10-09 12:01 ` [PATCH V7 4/8] MPX for amd64 Walfred Tedeschi
2013-10-09 12:01 ` [PATCH V7 7/8] Add MPX registers tests Walfred Tedeschi
2013-10-09 12:01 ` [PATCH V7 3/8] Add MPX support for i386 Walfred Tedeschi
2013-10-09 12:01 ` [PATCH V7 6/8] Add pretty-printer for MPX bnd registers Walfred Tedeschi
2013-10-09 12:01 ` [PATCH V7 8/8] Add MPX feature description to GDB manual Walfred Tedeschi
2013-11-18 20:26   ` Pedro Alves [this message]
2013-11-19  8:32     ` Tedeschi, Walfred
2013-10-09 12:01 ` [PATCH V7 1/8] Fix conditions in creating a bitfield Walfred Tedeschi
2013-10-09 12:02 ` [PATCH V7 2/8] Add MPX registers XML files Walfred Tedeschi
2013-10-20 19:23 ` [PATCH V7 0/8] Intel(R) MPX register support Mark Kettenis
2013-10-21 11:33   ` Tedeschi, Walfred
2013-11-04  9:07     ` Tedeschi, Walfred
2013-11-04 10:30       ` Mark Kettenis
2013-11-11  8:24         ` Tedeschi, Walfred
2013-11-11 10:12           ` Mark Kettenis
2013-11-11 11:48             ` Walfred Tedeschi
2013-11-19 10:28               ` Tedeschi, Walfred
2013-11-19 11:13                 ` Mark Kettenis
2013-11-19 12:15                   ` Tedeschi, Walfred
     [not found] ` <1381320034-4092-6-git-send-email-walfred.tedeschi@intel.com>
2013-11-19 15:14   ` [PATCH V7 5/8] Add MPX support to gdbserver Pedro Alves
2013-11-19 15:43     ` Tedeschi, Walfred

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=528A6878.2090903@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=tromey@redhat.com \
    --cc=walfred.tedeschi@intel.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