From: Pedro Alves <palves@redhat.com>
To: Pedro Alves <palves@redhat.com>,
Ajit Kumar Agarwal <ajit.kumar.agarwal@xilinx.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Michael Eager <eager@eagercon.com>,
Vinod Kathail <vinodk@xilinx.com>,
Vidhumouli Hunsigida <vidhum@xilinx.com>,
Nagaraju Mekala <nmekala@xilinx.com>
Subject: Re: [Patch, microblaze]: Communicate in larger blocks with the target.
Date: Tue, 17 Jun 2014 16:34:00 -0000 [thread overview]
Message-ID: <53A06E16.2020603@redhat.com> (raw)
In-Reply-To: <53A04753.5010102@redhat.com>
On 06/17/2014 02:49 PM, Pedro Alves wrote:
> On 06/17/2014 10:03 AM, Ajit Kumar Agarwal wrote:
>> Please find the following patch.
>>
>> [Patch, microblaze]: Communicate in larger blocks with the target.
>>
>> Communicate in larger blocks with the target. The chunk of memory
>> will be read from the target and then used in microblaze_analyze_prologue.
>> The above process minimizes the transaction with the Debug Agent.
>
> We have core infrustructure for this now, in the form of a
> code cache that reads ahead. Could you try using it?
> All you have to do is replace target_read_memory calls that are
> actually reading code, with target_read_code calls. See i386-tdep.c
> for example.
To be clear, I'm not talking about changing the new calls in your
patch, but instead, to change the existing calls. Then your
patch won't be necessary.
--
Pedro Alves
next prev parent reply other threads:[~2014-06-17 16:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 9:03 Ajit Kumar Agarwal
2014-06-17 13:49 ` Pedro Alves
2014-06-17 16:34 ` Pedro Alves [this message]
2014-06-17 16:49 ` Ajit Kumar Agarwal
2014-06-17 16:52 ` Pedro Alves
2014-06-17 18:09 ` Ajit Kumar Agarwal
2014-06-17 18:13 ` Ajit Kumar Agarwal
2014-06-18 9:28 ` Pedro Alves
2014-07-24 2:39 ` Michael Eager
2014-06-17 14:47 ` Michael Eager
2014-06-17 16:32 ` Tom Tromey
2014-07-23 18:56 ` Michael Eager
2014-07-23 20:04 ` Michael Eager
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=53A06E16.2020603@redhat.com \
--to=palves@redhat.com \
--cc=ajit.kumar.agarwal@xilinx.com \
--cc=eager@eagercon.com \
--cc=gdb-patches@sourceware.org \
--cc=nmekala@xilinx.com \
--cc=vidhum@xilinx.com \
--cc=vinodk@xilinx.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).