Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/3] Move the traceframe_available_memory code from memory_xfer_partial_1 down to the targets
Date: Fri, 21 Mar 2014 09:41:00 -0000	[thread overview]
Message-ID: <532C08BB.3080400@codesourcery.com> (raw)
In-Reply-To: <1394541731-27486-1-git-send-email-yao@codesourcery.com>

On 03/11/2014 08:42 PM, Yao Qi wrote:
> As a follow-up to
> 
>   [PATCH 7/8] Adjust read_value_memory to use to_xfer_partial
>   https://sourceware.org/ml/gdb-patches/2014-02/msg00384.html
> 
> this patch moves traceframe_available_memory down to the target side.
> After this patch, the gdb core code is cleaner, and code on handling
> unavailable memory is moved to remote/tfile/ctf targets.
> 
> In details, this patch moves traceframe_available_memory code from
> memory_xfer_partial_1 to remote target only, so remote target still
> uses traceframe_info mechanism to check unavailable memory, and use
> remote_ops to read them from read-only sections.  We don't use
> traceframe_info mechanism for tfile and ctf target, because it is
> fast to iterate all traceframes from trace file, so the summary
> information got from traceframe_info is not necessary.
> 
> This patch also moves two functions to remote.c from target.c,
> because they are only used in remote.c.  I'll clean them up in another
> patch.
> 
> This series is tested on x86_64-linux.
> 
> gdb:
> 
> 2014-03-11  Yao Qi  <yao@codesourcery.com>
> 
> 	* ctf.c (ctf_xfer_partial): Check the return value of
> 	exec_read_partial_read_only, if it is not TARGET_XFER_OK,
> 	return TARGET_XFER_UNAVAILABLE.
> 	* tracefile-tfile.c (tfile_xfer_partial): Likewise.
> 	* target.c (target_read_live_memory): Move it to remote.c.
> 	(memory_xfer_live_readonly_partial): Likewise.
> 	(memory_xfer_partial_1): Move some code to remote_read_bytes.
> 	* remote.c (target_read_live_memory): Moved from target.c.
> 	(memory_xfer_live_readonly_partial): Likewise.
> 	(remote_read_bytes): Moved from memory_xfer_partial_1.

Ping.  https://sourceware.org/ml/gdb-patches/2014-03/msg00262.html


-- 
Yao (齐尧)


  parent reply	other threads:[~2014-03-21  9:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-11 12:44 Yao Qi
2014-03-11 12:45 ` [PATCH 3/3] Remove target_read_live_memory Yao Qi
2014-03-21 12:01   ` Pedro Alves
2014-03-22 11:23     ` Yao Qi
2014-03-11 12:45 ` [PATCH 2/3] Factor remote_read_bytes Yao Qi
2014-03-21 11:57   ` Pedro Alves
2014-03-21  9:41 ` Yao Qi [this message]
2014-03-21 11:56 ` [PATCH 1/3] Move the traceframe_available_memory code from memory_xfer_partial_1 down to the targets Pedro Alves
2014-03-22 11:20   ` 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=532C08BB.3080400@codesourcery.com \
    --to=yao@codesourcery.com \
    --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