qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: tan_hong_ze <tan_hong_ze@163.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] target/loongarch: Enables plugins to get instruction codes
Date: Thu, 30 Mar 2023 14:56:43 +0100	[thread overview]
Message-ID: <87mt3uny00.fsf@linaro.org> (raw)
In-Reply-To: <20230330113806.1458040-1-tan_hong_ze@163.com>


tan_hong_ze <tan_hong_ze@163.com> writes:

> Signed-off-by: tan_hong_ze <tan_hong_ze@163.com>
> ---
>  target/loongarch/translate.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/target/loongarch/translate.c b/target/loongarch/translate.c
> index 3bb63bfb3e..50d6b62f39 100644
> --- a/target/loongarch/translate.c
> +++ b/target/loongarch/translate.c
> @@ -198,7 +198,7 @@ static void loongarch_tr_translate_insn(DisasContextBase *dcbase, CPUState *cs)
>      CPULoongArchState *env = cs->env_ptr;
>      DisasContext *ctx = container_of(dcbase, DisasContext, base);
>  
> -    ctx->opcode = cpu_ldl_code(env, ctx->base.pc_next);
> +    ctx->opcode = translator_ldl(env, &ctx->base, ctx->base.pc_next);
>  
>      if (!decode(ctx, ctx->opcode)) {
>          qemu_log_mask(LOG_UNIMP, "Error: unknown opcode. "

Acked-by: Alex Bennée <alex.bennee@linaro.org>

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


  reply	other threads:[~2023-03-30 13:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 11:38 [PATCH] target/loongarch: Enables plugins to get instruction codes tan_hong_ze
2023-03-30 13:56 ` Alex Bennée [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-22  7:56 谭弘泽
2023-03-22 12:31 ` Richard Henderson

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=87mt3uny00.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=tan_hong_ze@163.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;
as well as URLs for NNTP newsgroup(s).