From: Walfred Tedeschi <walfred.tedeschi@intel.com>
To: tromey@redhat.com, gdb-patches@sourceware.org, mark.kettenis@xs4all.nl
Cc: Walfred Tedeschi <walfred.tedeschi@intel.com>
Subject: [PATCH V5 8/8] Add MPX feature description to GDB manual.
Date: Mon, 09 Sep 2013 12:25:00 -0000 [thread overview]
Message-ID: <1378729481-9105-9-git-send-email-walfred.tedeschi@intel.com> (raw)
In-Reply-To: <1378729481-9105-1-git-send-email-walfred.tedeschi@intel.com>
Describes MPX feature registers including bnd0raw ... bnd3raw, bnd0 ... bnd3
bndstatus and bndcfgu. News adds the section for Intel(R) Architecture
Instructions Extensions and mention the MPX support.
2013-08-30 Walfred Tedeschi <walfred.tedeschi>
* NEWS: Add section for Intel(R) Architecture Instructions
Extesions mentioning MPX.
doc/
* gdb.texinfo (i386 Features): Add MPX feature.
---
gdb/NEWS | 2 ++
gdb/doc/gdb.texinfo | 25 +++++++++++++++++++++++++
2 files changed, 27 insertions(+)
diff --git a/gdb/NEWS b/gdb/NEWS
index ca8baea..fc58cc4 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -5464,3 +5464,5 @@ GDB now handles cross debugging. If you are remotely debugging between
two different machines, type ``./configure host -target=targ''.
Host is the machine where GDB will run; targ is the machine
where the program that you are debugging will run.
+
+ * GDB now supports access to Intel(R) MPX registers on GNU/Linux.
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 21250fe..353c389 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -42560,6 +42560,31 @@ describe the upper 128 bits of @sc{ymm} registers:
@samp{ymm0h} through @samp{ymm15h} for amd64
@end itemize
+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. 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:
+
+@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}.
--
1.7.10.4
next prev parent reply other threads:[~2013-09-09 12:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 12:25 [PATCH V4 0/8] Intel(R) MPX register support Walfred Tedeschi
2013-09-09 12:24 ` [PATCH V5 1/8] Fix conditions in creating a bitfield Walfred Tedeschi
2013-09-09 12:25 ` [PATCH V5 5/8] Add MPX support to gdbserver Walfred Tedeschi
2013-09-09 12:25 ` [PATCH V5 7/8] Add MPX registers tests Walfred Tedeschi
2013-09-09 12:25 ` [PATCH V5 2/8] Add MPX registers XML files Walfred Tedeschi
2013-09-09 12:25 ` Walfred Tedeschi [this message]
2013-09-09 16:35 ` [PATCH V5 8/8] Add MPX feature description to GDB manual Eli Zaretskii
2013-09-09 12:25 ` [PATCH V5 4/8] MPX for amd64 Walfred Tedeschi
2013-09-09 12:25 ` [PATCH V5 3/8] Add MPX support for i386 Walfred Tedeschi
2013-09-09 12:25 ` [PATCH V5 6/8] Add pretty-printer for MPX bnd registers Walfred Tedeschi
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=1378729481-9105-9-git-send-email-walfred.tedeschi@intel.com \
--to=walfred.tedeschi@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=tromey@redhat.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