From: Yao Qi <qiyaoltc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: Don Breazeal <donb@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Optimize memory_xfer_partial for remote
Date: Tue, 21 Jun 2016 10:15:00 -0000 [thread overview]
Message-ID: <86mvmergpe.fsf@gmail.com> (raw)
In-Reply-To: <f1b1220d-1ec8-b9e7-2783-616e7d7e4eb1@redhat.com> (Pedro Alves's message of "Mon, 20 Jun 2016 20:25:47 +0100")
Pedro Alves <palves@redhat.com> writes:
> So seems to be we should have a real target_get_memory_xfer_limit()
> (or some such) target method.
Alternatively, we can move breakpoint_xfer_memory down to each target
(remote, native, etc), on which we know what limit it is.
--
Yao (齐尧)
next prev parent reply other threads:[~2016-06-21 10:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 19:02 Don Breazeal
2016-06-20 15:31 ` [PING] " Don Breazeal
2016-06-20 19:25 ` Pedro Alves
2016-06-21 10:15 ` Yao Qi [this message]
2016-06-24 21:21 ` [PATCH v2] " Don Breazeal
2016-06-24 22:23 ` Pedro Alves
2016-06-27 20:23 ` Don Breazeal
2016-06-30 17:06 ` Pedro Alves
2016-06-30 17:45 ` Don Breazeal
2016-06-30 18:40 ` Pedro Alves
2016-06-30 22:40 ` [PATCH v3] " Don Breazeal
2016-06-30 23:44 ` Pedro Alves
2016-07-01 18:24 ` [pushed] " Don Breazeal
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=86mvmergpe.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=donb@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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