From: Yao Qi <yao@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 5/5] set/show code-cache NEWS and doc
Date: Thu, 24 Oct 2013 08:26:00 -0000 [thread overview]
Message-ID: <5268D967.2000703@codesourcery.com> (raw)
In-Reply-To: <83sivshuux.fsf@gnu.org>
On 10/23/2013 11:25 PM, Eli Zaretskii wrote:
> Thanks. However, this (and even more importantly, the manual) should
> explain what is "code" in this context. "Code" is too general a word
> to hope that the reader will immediately understand what you mean.
>
I go through gdb.texinfo, and find "program code" is used in some
places. I choose it.
> Also, the last sentence above should be in the manual; it's not good
> that the manual has less details than NEWS.
OK, add one line in the manual to mention that this improves
disassemble. How about this?
--
Yao (é½å°§)
gdb:
2013-10-23 Yao Qi <yao@codesourcery.com>
* NEWS: Add note on new "set code-cache" option.
gdb/doc:
2013-10-23 Yao Qi <yao@codesourcery.com>
* gdb.texinfo (Caching Remote Data): Document new
`set/show stack-cache' option.
---
gdb/NEWS | 6 ++++++
gdb/doc/gdb.texinfo | 15 ++++++++++++++-
2 files changed, 20 insertions(+), 1 deletions(-)
diff --git a/gdb/NEWS b/gdb/NEWS
index 10834df..10d5804 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -98,6 +98,12 @@ set range-stepping
show range-stepping
Control whether target-assisted range stepping is enabled.
+set code-cache
+show code-cache
+ Use more aggressive caching for accesses to the program code. This
+ improves performance of remote debugging (particularly disassemble)
+ without affecting correctness.
+
* You can now use a literal value 'unlimited' for options that
interpret 0 or -1 as meaning "unlimited". E.g., "set
trace-buffer-size unlimited" is now an alias for "set
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 44fb174..5770382 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -10796,7 +10796,8 @@ Therefore, by default, @value{GDBN} only caches data
known to be on the stack@footnote{In non-stop mode, it is moderately
rare for a running thread to modify the stack of a stopped thread
in a way that would interfere with a backtrace, and caching of
-stack reads provides a significant speed up of remote backtraces.}.
+stack reads provides a significant speed up of remote backtraces.} or
+in the program code.
Other regions of memory can be explicitly marked as
cacheable; see @pxref{Memory Region Attributes}.
@@ -10821,6 +10822,18 @@ caching. By default, this option is @code{ON}.
@item show stack-cache
Show the current state of data caching for memory accesses.
+@kindex set code-cache
+@item set code-cache on
+@itemx set code-cache off
+Enable or disable caching of program code accesses. When @code{ON},
+use caching. By default, this option is @code{ON}. This improves
+performance of disassemble in remote debugging without affecting
+correctness.
+
+@kindex show code-cache
+@item show code-cache
+Show the current state of data caching for program code accesses.
+
@kindex info dcache
@item info dcache @r{[}line@r{]}
Print the information about the data cache performance. The
--
1.7.7.6
next prev parent reply other threads:[~2013-10-24 8:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 8:29 [PATCH 0/5] Cache code access for disassemble Yao Qi
2013-10-23 8:29 ` [PATCH 3/5] set/show code-cache Yao Qi
2013-10-25 7:47 ` Doug Evans
2013-10-25 14:35 ` Yao Qi
2013-10-25 15:57 ` Doug Evans
2013-10-26 13:24 ` Yao Qi
2013-10-28 18:33 ` Doug Evans
2013-10-23 8:29 ` [PATCH 4/5] Use target_read_code in disassemble Yao Qi
2013-10-23 8:29 ` [PATCH 5/5] set/show code-cache NEWS and doc Yao Qi
2013-10-23 15:25 ` Eli Zaretskii
2013-10-24 8:26 ` Yao Qi [this message]
2013-10-24 15:21 ` Eli Zaretskii
[not found] ` <526A3B07.1020607@codesourcery.com>
2013-10-25 10:01 ` Eli Zaretskii
2013-11-02 0:25 ` Yao Qi
2013-11-02 7:06 ` Eli Zaretskii
2013-10-23 8:29 ` [PATCH 1/5] Add REGISTRY for struct address_space Yao Qi
2013-10-28 20:46 ` Tom Tromey
2013-10-23 8:29 ` [PATCH 2/5] Associate target_dcache to address_space Yao Qi
2013-10-23 16:37 ` Tom Tromey
2013-10-24 8:33 ` Yao Qi
2013-10-28 20:49 ` Tom Tromey
2013-10-28 21:51 ` Doug Evans
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=5268D967.2000703@codesourcery.com \
--to=yao@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.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