Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/5] Associate target_dcache to address_space.
Date: Mon, 28 Oct 2013 21:51:00 -0000	[thread overview]
Message-ID: <CADPb22Sgu8EqfVP8_sWf63O-_Jc9PwMuoW+G2po2Tz4XExU98A@mail.gmail.com> (raw)
In-Reply-To: <1382516855-32218-3-git-send-email-yao@codesourcery.com>

On Wed, Oct 23, 2013 at 1:27 AM, Yao Qi <yao@codesourcery.com> wrote:
> Hi,
> Nowadays, 'target_dcache' is a global variable in GDB, which is not
> necessary.  It can be a per-address-space variable.  In this patch, we
> add a new structure 'target_dcache', which includes all dcaches of
> target and all of them are per-address-space.
>
> There is one field 'general' which is equivalent to current
> variable 'target_dcache'.  I thought to name it 'stack', but it also
> cache memory regions marked by attributes, I choose 'general'.
>
> gdb:
>
> 2013-10-23  Yao Qi  <yao@codesourcery.com>
>
>         * progspace.h (struct address_space): Declare.
>         (current_address_space): New macro.
>         * target.c (target_dcache_aspace_key): New.
>         (target_dcache): Delete.
>         (struct target_dcache): New.
>         (target_dcache_alloc): New function.
>         (target_dcache_xfree): New function.
>         (target_dcache_get): New function.
>         (target_dcache_cleanup)): New function.
>         (target_dcache_invalidate): Update.
>         (memory_xfer_partial_1): Update.
>         (initialize_targets): Initialize target_dcache_aspace_key.
> [...]
> +/* Allocate an instance of struct target_dcache.  */
> +
> +static struct target_dcache *
> +target_dcache_alloc (void)
> +{
> +  struct target_dcache *dcache = xmalloc (sizeof (*dcache));
> +
> +  dcache->general = dcache_init ();
> +
> +  return dcache;
> +}

I think more work is needed here.
I looked for it in the patch series, apologies if I missed it!

Consider "info dcache" and "set dcache size,line-size".

They use a nasty global, last_cache, which needs to go away.

Plus, we need to specify their semantics in a cache-per-address-space world.


      parent reply	other threads:[~2013-10-28 21:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-23  8:29 [PATCH 0/5] Cache code access for disassemble Yao Qi
2013-10-23  8:29 ` [PATCH 3/5] set/show code-cache Yao Qi
2013-10-25  7:47   ` Doug Evans
2013-10-25 14:35     ` Yao Qi
2013-10-25 15:57       ` Doug Evans
2013-10-26 13:24         ` Yao Qi
2013-10-28 18:33           ` Doug Evans
2013-10-23  8:29 ` [PATCH 4/5] Use target_read_code in disassemble Yao Qi
2013-10-23  8:29 ` [PATCH 5/5] set/show code-cache NEWS and doc Yao Qi
2013-10-23 15:25   ` Eli Zaretskii
2013-10-24  8:26     ` Yao Qi
2013-10-24 15:21       ` Eli Zaretskii
     [not found]         ` <526A3B07.1020607@codesourcery.com>
2013-10-25 10:01           ` Eli Zaretskii
2013-11-02  0:25             ` Yao Qi
2013-11-02  7:06               ` Eli Zaretskii
2013-10-23  8:29 ` [PATCH 1/5] Add REGISTRY for struct address_space Yao Qi
2013-10-28 20:46   ` Tom Tromey
2013-10-23  8:29 ` [PATCH 2/5] Associate target_dcache to address_space Yao Qi
2013-10-23 16:37   ` Tom Tromey
2013-10-24  8:33     ` Yao Qi
2013-10-28 20:49       ` Tom Tromey
2013-10-28 21:51   ` 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=CADPb22Sgu8EqfVP8_sWf63O-_Jc9PwMuoW+G2po2Tz4XExU98A@mail.gmail.com \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=yao@codesourcery.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