qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Edgar E. Iglesias" <edgar.iglesias@xilinx.com>
To: Joe Komlodi <joe.komlodi@xilinx.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH V2 3/4] target/microblaze: gdb: Fix incorrect SReg reporting
Date: Thu, 14 May 2020 15:50:07 +0200	[thread overview]
Message-ID: <20200514135007.GS2945@toto> (raw)
In-Reply-To: <1589393329-223076-3-git-send-email-komlodi@xilinx.com>

On Wed, May 13, 2020 at 11:08:47AM -0700, Joe Komlodi wrote:
> SRegs used to be reported to GDB by iterating over the SRegs array,
> however we do not store them in an order that allows them to be
> reported to GDB in that way.
> 
> To fix this, a simple map is used to map the register GDB wants to its
> location in the SRegs array.

Reviewed-by: Edgar E. Iglesias <edgar.iglesias@xilinx.com>


> 
> Signed-off-by: Joe Komlodi <komlodi@xilinx.com>
> ---
>  target/microblaze/gdbstub.c | 59 +++++++++++++++++++++++++++++++++++++--------
>  1 file changed, 49 insertions(+), 10 deletions(-)
> 
> diff --git a/target/microblaze/gdbstub.c b/target/microblaze/gdbstub.c
> index af29f00..485b717 100644
> --- a/target/microblaze/gdbstub.c
> +++ b/target/microblaze/gdbstub.c
> @@ -25,6 +25,21 @@ int mb_cpu_gdb_read_register(CPUState *cs, GByteArray *mem_buf, int n)
>  {
>      MicroBlazeCPU *cpu = MICROBLAZE_CPU(cs);
>      CPUMBState *env = &cpu->env;
> +    /*
> +     * GDB expects SREGs in the following order:
> +     * PC, MSR, EAR, ESR, FSR, BTR, EDR, PID, ZPR, TLBX, TLBSX, TLBLO, TLBHI.
> +     * They aren't stored in this order, so make a map.
> +     * PID, ZPR, TLBx, TLBsx, TLBLO, and TLBHI aren't modeled, so we don't
> +     * map them to anything and return a value of 0 instead.
> +     */
> +    static const uint8_t sreg_map[6] = {
> +        SR_PC,
> +        SR_MSR,
> +        SR_EAR,
> +        SR_ESR,
> +        SR_FSR,
> +        SR_BTR
> +    };
>  
>      /*
>       * GDB expects registers to be reported in this order:
> @@ -40,15 +55,16 @@ int mb_cpu_gdb_read_register(CPUState *cs, GByteArray *mem_buf, int n)
>          n -= 32;
>          switch (n) {
>          case 0 ... 5:
> -            return gdb_get_reg32(mem_buf, env->sregs[n]);
> +            return gdb_get_reg32(mem_buf, env->sregs[sreg_map[n]]);
>          /* PVR12 is intentionally skipped */
>          case 6 ... 17:
>              n -= 6;
>              return gdb_get_reg32(mem_buf, env->pvr.regs[n]);
> -        case 18 ... 24:
> -            /* Add an offset of 6 to resume where we left off with SRegs */
> -            n = n - 18 + 6;
> -            return gdb_get_reg32(mem_buf, env->sregs[n]);
> +        case 18:
> +            return gdb_get_reg32(mem_buf, env->sregs[SR_EDR]);
> +        /* Other SRegs aren't modeled, so report a value of 0 */
> +        case 19 ... 24:
> +            return gdb_get_reg32(mem_buf, 0);
>          case 25:
>              return gdb_get_reg32(mem_buf, env->slr);
>          case 26:
> @@ -66,29 +82,52 @@ int mb_cpu_gdb_write_register(CPUState *cs, uint8_t *mem_buf, int n)
>      CPUMBState *env = &cpu->env;
>      uint32_t tmp;
>  
> +    /*
> +     * GDB expects SREGs in the following order:
> +     * PC, MSR, EAR, ESR, FSR, BTR, EDR, PID, ZPR, TLBX, TLBSX, TLBLO, TLBHI.
> +     * They aren't stored in this order, so make a map.
> +     * PID, ZPR, TLBx, TLBsx, TLBLO, and TLBHI aren't modeled, so we don't
> +     * map them to anything.
> +     */
> +    static const uint8_t sreg_map[6] = {
> +        SR_PC,
> +        SR_MSR,
> +        SR_EAR,
> +        SR_ESR,
> +        SR_FSR,
> +        SR_BTR
> +    };
> +
>      if (n > cc->gdb_num_core_regs) {
>          return 0;
>      }
>  
>      tmp = ldl_p(mem_buf);
>  
> +    /*
> +     * GDB expects registers to be reported in this order:
> +     * R0-R31
> +     * PC-BTR
> +     * PVR0-PVR11
> +     * EDR-TLBHI
> +     * SLR-SHR
> +     */
>      if (n < 32) {
>          env->regs[n] = tmp;
>      } else {
>          n -= 32;
>          switch (n) {
>          case 0 ... 5:
> -            env->sregs[n] = tmp;
> +            env->sregs[sreg_map[n]] = tmp;
>              break;
>          /* PVR12 is intentionally skipped */
>          case 6 ... 17:
>              n -= 6;
>              env->pvr.regs[n] = tmp;
>              break;
> -        case 18 ... 24:
> -            /* Add an offset of 6 to resume where we left off with SRegs */
> -            n = n - 18 + 6;
> -            env->sregs[n] = tmp;
> +        /* Only EDR is modeled in these indeces, so ignore the rest */
> +        case 18:
> +            env->sregs[SR_EDR] = tmp;
>              break;
>          case 25:
>              env->slr = tmp;
> -- 
> 2.7.4
> 


  reply	other threads:[~2020-05-14 13:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13 18:08 [PATCH V2 1/4] target/microblaze: gdb: Add dynamic GDB XML register support Joe Komlodi
2020-05-13 18:08 ` [PATCH V2 2/4] target/microblaze: gdb: Extend the number of registers presented to GDB Joe Komlodi
2020-05-14 13:49   ` Edgar E. Iglesias
2020-05-13 18:08 ` [PATCH V2 3/4] target/microblaze: gdb: Fix incorrect SReg reporting Joe Komlodi
2020-05-14 13:50   ` Edgar E. Iglesias [this message]
2020-05-13 18:08 ` [PATCH V2 4/4] target/microblaze: monitor: Increase the number of registers reported Joe Komlodi
2020-05-14 13:50   ` Edgar E. Iglesias
2020-05-13 18:08 ` [PATCH V2 0/4] target/microblaze: Add GDB XML and correct SReg reporting Joe Komlodi
2020-05-14 13:52   ` Edgar E. Iglesias
2020-05-14 13:41 ` [PATCH V2 1/4] target/microblaze: gdb: Add dynamic GDB XML register support Edgar E. Iglesias
2020-05-14 17:05   ` Joe Komlodi

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=20200514135007.GS2945@toto \
    --to=edgar.iglesias@xilinx.com \
    --cc=joe.komlodi@xilinx.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).