Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: gdb-patches@sourceware.org
Cc: Pedro Alves <pedro@codesourcery.com>,
	Michael Snyder <msnyder@vmware.com>,
	        Hui Zhu <teawater@gmail.com>,
	Marc Khouzam <marc.khouzam@ericsson.com>,
	        Greg Law <glaw@undo-software.com>
Subject: Re: [patch] only update dcache after write succeeds
Date: Tue, 15 Sep 2009 06:58:00 -0000	[thread overview]
Message-ID: <e394668d0909142357u43080d63p1be005f3b5643d1c@mail.gmail.com> (raw)
In-Reply-To: <20090914191657.E32D6844C3@localhost>

On Mon, Sep 14, 2009 at 12:16 PM, Doug Evans <dje@google.com> wrote:
> Hi.
>
> Marc, Greg: Can you see if this patch fixes things for you?
>
> 2009-09-14  Doug Evans  <dje@google.com>
>
>        * target.c (memory_xfer_partial): Only update dcache after we know
>        the write succeeded.
>
> Index: target.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/target.c,v
> retrieving revision 1.223
> diff -u -p -r1.223 target.c
> --- target.c    8 Sep 2009 23:52:45 -0000       1.223
> +++ target.c    14 Sep 2009 19:11:38 -0000
> @@ -1289,19 +1289,6 @@ memory_xfer_partial (struct target_ops *
>        }
>     }
>
> -  /* Make sure the cache gets updated no matter what - if we are writing
> -     to the stack, even if this write is not tagged as such, we still need
> -     to update the cache. */
> -
> -  if (inf != NULL
> -      && readbuf == NULL
> -      && !region->attrib.cache
> -      && stack_cache_enabled_p
> -      && object != TARGET_OBJECT_STACK_MEMORY)
> -    {
> -      dcache_update (target_dcache, memaddr, (void *) writebuf, reg_len);
> -    }
> -
>   /* If none of those methods found the memory we wanted, fall back
>      to a target partial transfer.  Normally a single call to
>      to_xfer_partial is enough; if it doesn't recognize an object
> @@ -1331,6 +1318,20 @@ memory_xfer_partial (struct target_ops *
>   if (readbuf && !show_memory_breakpoints)
>     breakpoint_restore_shadows (readbuf, memaddr, reg_len);
>
> +  /* Make sure the cache gets updated no matter what - if we are writing
> +     to the stack.  Even if this write is not tagged as such, we still need
> +     to update the cache.  */
> +
> +  if (res > 0
> +      && inf != NULL
> +      && writebuf != NULL
> +      && !region->attrib.cache
> +      && stack_cache_enabled_p
> +      && object != TARGET_OBJECT_STACK_MEMORY)
> +    {
> +      dcache_update (target_dcache, memaddr, (void *) writebuf, reg_len);
> +    }
> +
>   /* If we still haven't got anything, return the last error.  We
>      give up.  */
>   return res;
>

Of course I did forget to pass the correct length.

009-09-14  Doug Evans  <dje@google.com>

        * target.c (memory_xfer_partial): Pass correct length to dcache_update.

Index: target.c
===================================================================
RCS file: /cvs/src/src/gdb/target.c,v
retrieving revision 1.225
diff -u -p -r1.225 target.c
--- target.c    15 Sep 2009 03:30:06 -0000      1.225
+++ target.c    15 Sep 2009 06:54:16 -0000
@@ -1333,7 +1333,7 @@ memory_xfer_partial (struct target_ops *
       && stack_cache_enabled_p
       && object != TARGET_OBJECT_STACK_MEMORY)
     {
-      dcache_update (target_dcache, memaddr, (void *) writebuf, reg_len);
+      dcache_update (target_dcache, memaddr, (void *) writebuf, res);
     }

   /* If we still haven't got anything, return the last error.  We


      parent reply	other threads:[~2009-09-15  6:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-14 19:17 Doug Evans
2009-09-14 19:26 ` Michael Snyder
2009-09-14 19:29   ` Marc Khouzam
2009-09-14 20:21     ` Michael Snyder
2009-09-14 19:43   ` Doug Evans
2009-09-14 20:20     ` Michael Snyder
2009-09-14 20:40       ` Pedro Alves
2009-09-14 20:43         ` Michael Snyder
2009-09-14 20:41       ` Doug Evans
2009-09-14 20:45         ` Michael Snyder
2009-09-14 19:26 ` Greg Law
2009-09-14 19:28   ` Marc Khouzam
2009-09-15  0:11 ` Hui Zhu
2009-09-15  6:58 ` Doug Evans [this message]

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=e394668d0909142357u43080d63p1be005f3b5643d1c@mail.gmail.com \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=glaw@undo-software.com \
    --cc=marc.khouzam@ericsson.com \
    --cc=msnyder@vmware.com \
    --cc=pedro@codesourcery.com \
    --cc=teawater@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