Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: Doug Evans <xdje42@gmail.com>
Cc: Pedro Alves <palves@redhat.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Delegate to target_ops->beneath to read cache lines
Date: Mon, 02 Dec 2013 06:07:00 -0000	[thread overview]
Message-ID: <529C232A.7080900@codesourcery.com> (raw)
In-Reply-To: <CAP9bCMTpcUJ_Okp8XwBhCQefsKrfkUo4iKcrv8B_Xip4Hc+h8w@mail.gmail.com>

On 11/30/2013 03:42 AM, Doug Evans wrote:
> I think a comment is required here explaining why things are the way they are.
> i.e., why we use current_target.beneath instead of &current_target.

I find the comments in target_read_memory can do some explanations,
so I copy that paragraph here.  Is it clear to you?

-- 
Yao (齐尧)

gdb:

2013-12-02  Yao Qi  <yao@codesourcery.com>

	* dcache.c (dcache_read_line): Add comments.
---
 gdb/dcache.c |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/gdb/dcache.c b/gdb/dcache.c
index 12d1a4b..0707cdf 100644
--- a/gdb/dcache.c
+++ b/gdb/dcache.c
@@ -337,6 +337,9 @@ dcache_read_line (DCACHE *dcache, struct dcache_block *db)
 	  continue;
 	}
 
+      /* Dispatch to the topmost target, not the flattened current_target.
+	 Memory accesses check target->to_has_(all_)memory, and the
+	 flattened target doesn't inherit those.  */
       res = target_read (current_target.beneath, TARGET_OBJECT_RAW_MEMORY,
 			 NULL, myaddr, memaddr, reg_len);
       if (res < reg_len)
-- 
1.7.7.6


  parent reply	other threads:[~2013-12-02  6:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-27 12:41 Yao Qi
2013-11-27 15:27 ` Pedro Alves
2013-11-29 11:12   ` Yao Qi
2013-11-29 13:47     ` Pedro Alves
2013-11-29 14:00       ` Yao Qi
2013-11-29 14:27         ` Pedro Alves
2013-11-29 20:06     ` Doug Evans
2013-11-29 20:16       ` Pedro Alves
2013-12-02  6:07       ` Yao Qi [this message]
2013-12-02 10:36         ` Pedro Alves
2013-12-02 11:04           ` Yao Qi
2013-12-02 11:12             ` Pedro Alves

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=529C232A.7080900@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=xdje42@gmail.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