All of lore.kernel.org
 help / color / mirror / Atom feed
From: Song Gao <gaosong@loongson.cn>
To: qemu-devel@nongnu.org
Cc: richard.henderson@linaro.org, laurent@vivier.eu,
	gaosong@loongson.cn, Xiaojuan Yang <yangxiaojuan@loongson.cn>
Subject: [PATCH v19 07/13] target/loongarch: remove badaddr from CPULoongArch
Date: Thu, 23 Jun 2022 16:55:20 +0800	[thread overview]
Message-ID: <20220623085526.1678168-8-gaosong@loongson.cn> (raw)
In-Reply-To: <20220623085526.1678168-1-gaosong@loongson.cn>

We can use CSR_BADV to replace badaddr.

Signed-off-by: Song Gao <gaosong@loongson.cn>
Signed-off-by: Xiaojuan Yang <yangxiaojuan@loongson.cn>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
---
 target/loongarch/cpu.h     | 2 --
 target/loongarch/gdbstub.c | 2 +-
 2 files changed, 1 insertion(+), 3 deletions(-)

diff --git a/target/loongarch/cpu.h b/target/loongarch/cpu.h
index 71a5036c3c..4b4fbcdc71 100644
--- a/target/loongarch/cpu.h
+++ b/target/loongarch/cpu.h
@@ -246,8 +246,6 @@ typedef struct CPUArchState {
     uint64_t lladdr; /* LL virtual address compared against SC */
     uint64_t llval;
 
-    uint64_t badaddr;
-
     /* LoongArch CSRs */
     uint64_t CSR_CRMD;
     uint64_t CSR_PRMD;
diff --git a/target/loongarch/gdbstub.c b/target/loongarch/gdbstub.c
index 0c48834201..24e126fb2d 100644
--- a/target/loongarch/gdbstub.c
+++ b/target/loongarch/gdbstub.c
@@ -21,7 +21,7 @@ int loongarch_cpu_gdb_read_register(CPUState *cs, GByteArray *mem_buf, int n)
     } else if (n == 32) {
         return gdb_get_regl(mem_buf, env->pc);
     } else if (n == 33) {
-        return gdb_get_regl(mem_buf, env->badaddr);
+        return gdb_get_regl(mem_buf, env->CSR_BADV);
     }
     return 0;
 }
-- 
2.31.1



  parent reply	other threads:[~2022-06-23  8:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23  8:55 [PATCH v19 00/13] Add LoongArch linux-user emulation support Song Gao
2022-06-23  8:55 ` [PATCH v19 01/13] linux-user: Add LoongArch generic header files Song Gao
2022-06-23  8:55 ` [PATCH v19 02/13] linux-user: Add LoongArch signal support Song Gao
2022-06-23 23:34   ` Richard Henderson
2022-06-24  0:45     ` maobibo
2022-06-24  1:13       ` maobibo
2022-06-24  1:20       ` Richard Henderson
2022-06-24  1:41         ` gaosong
2022-06-23  8:55 ` [PATCH v19 03/13] linux-user: Add LoongArch elf support Song Gao
2022-06-23  8:55 ` [PATCH v19 04/13] linux-user: Add LoongArch syscall support Song Gao
2022-06-23  8:55 ` [PATCH v19 05/13] linux-user: Add LoongArch cpu_loop support Song Gao
2022-06-23  8:55 ` [PATCH v19 06/13] scripts: add loongarch64 binfmt config Song Gao
2022-06-23  8:55 ` Song Gao [this message]
2022-06-23  8:55 ` [PATCH v19 08/13] target/loongarch: Fix missing update CSR_BADV Song Gao
2022-06-23  8:55 ` [PATCH v19 09/13] target/loongarch: Fix helper_asrtle_d/asrtgt_d raise wrong exception Song Gao
2022-06-23  8:55 ` [PATCH v19 10/13] target/loongarch: remove unused include hw/loader.h Song Gao
2022-06-23  8:55 ` [PATCH v19 11/13] target/loongarch: Adjust functions and structure to support user-mode Song Gao
2022-06-23  8:55 ` [PATCH v19 12/13] default-configs: Add loongarch linux-user support Song Gao
2022-06-23  8:55 ` [PATCH v19 13/13] target/loongarch: Update README Song Gao

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=20220623085526.1678168-8-gaosong@loongson.cn \
    --to=gaosong@loongson.cn \
    --cc=laurent@vivier.eu \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=yangxiaojuan@loongson.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.