From: Eli Zaretskii <eliz@gnu.org>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/3] set/show code-cache
Date: Thu, 21 Nov 2013 05:06:00 -0000 [thread overview]
Message-ID: <83mwkye7ii.fsf@gnu.org> (raw)
In-Reply-To: <528D781A.7070909@codesourcery.com>
> Date: Thu, 21 Nov 2013 11:03:54 +0800
> From: Yao Qi <yao@codesourcery.com>
>
> I update this patch for the name of some variables, after we discussed
> in patch 1/3. I'll commit it in two days.
Thanks.
> gdb/NEWS | 6 +++++
> gdb/doc/gdb.texinfo | 16 ++++++++++++++-
These parts are OK.
> + add_setshow_boolean_cmd ("code-cache", class_support,
> + &code_cache_enabled_1, _("\
> +Set cache use for code segment access."), _("\
> +Show cache use for code segment access."), _("\
> +When on, use the target memory cache for all code segment access,\n\
^^^^^^
"accesses"
> +regardless of any configured memory regions. This improves remote\n\
> +performance significantly. By default, caching for code segment\n\
> +access is on."),
next prev parent reply other threads:[~2013-11-21 3:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 1:34 [PATCH 0/3 V3] Cache code access for disassemble Yao Qi
2013-11-21 1:18 ` [PATCH 1/3] Renaming in target-dcache.c Yao Qi
2013-11-21 1:47 ` Doug Evans
2013-11-21 3:05 ` Yao Qi
2013-11-21 1:18 ` [PATCH 3/3] Use target_read_code in disassemble Yao Qi
2013-11-21 2:56 ` Doug Evans
2013-11-21 1:18 ` [PATCH 2/3] set/show code-cache Yao Qi
2013-11-21 3:33 ` Yao Qi
2013-11-21 5:06 ` Eli Zaretskii [this message]
2013-11-21 12:21 ` Pedro Alves
2013-11-21 14:03 ` Yao Qi
2013-11-21 16:13 ` Eli Zaretskii
2013-11-22 1:51 ` Yao Qi
2013-11-21 20:50 ` Doug Evans
2013-11-21 19:38 ` Tom Tromey
2013-11-21 21:06 ` Doug Evans
2013-11-21 21:17 ` Tom Tromey
2013-11-22 0:38 ` Doug Evans
2013-11-22 2:19 ` Yao Qi
2013-11-22 7:43 ` Eli Zaretskii
2013-11-24 9:02 ` [PATCH 0/3 V3] Cache code access for disassemble Yao Qi
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=83mwkye7ii.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=yao@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