qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>, Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH] accel/tcg: Add CPU_LOG_EXEC tracing for cpu_io_recompile()
Date: Tue, 13 Oct 2020 16:18:24 -0700	[thread overview]
Message-ID: <bb8c6347-e127-941a-c9b6-fd01cdb09afb@linaro.org> (raw)
In-Reply-To: <20201013122658.4620-1-peter.maydell@linaro.org>

On 10/13/20 5:26 AM, Peter Maydell wrote:
> When using -icount, it's useful for the CPU_LOG_EXEC logging
> to include information about when cpu_io_recompile() was
> called, because it alerts the reader of the log that the
> tracing of a previous TB execution may not actually
> correspond to an actually executed instruction. For instance
> if you're using -icount and also -singlestep then a guest
> instruction that makes an IO access appears in two
> "Trace" lines, once in a TB that triggers the cpu_io_recompile()
> and then again in the TB that actually executes.
> 
> (This is a similar reason to why the "Stopped execution of
> TB chain before..." logging in cpu_tb_exec() is helpful
> when trying to track execution flow in the logs.)
> 
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>

Thanks, queued to tcg-next.


r~

> ---
>  accel/tcg/translate-all.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/accel/tcg/translate-all.c b/accel/tcg/translate-all.c
> index d76097296df..4572b4901fb 100644
> --- a/accel/tcg/translate-all.c
> +++ b/accel/tcg/translate-all.c
> @@ -2267,6 +2267,10 @@ void cpu_io_recompile(CPUState *cpu, uintptr_t retaddr)
>          tb_destroy(tb);
>      }
>  
> +    qemu_log_mask_and_addr(CPU_LOG_EXEC, tb->pc,
> +                           "cpu_io_recompile: rewound execution of TB to "
> +                           TARGET_FMT_lx "\n", tb->pc);
> +
>      /* TODO: If env->pc != tb->pc (i.e. the faulting instruction was not
>       * the first in the TB) then we end up generating a whole new TB and
>       *  repeating the fault, which is horribly inefficient.
> 



      reply	other threads:[~2020-10-13 23:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13 12:26 [PATCH] accel/tcg: Add CPU_LOG_EXEC tracing for cpu_io_recompile() Peter Maydell
2020-10-13 23:18 ` Richard Henderson [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=bb8c6347-e127-941a-c9b6-fd01cdb09afb@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).