From: Richard Henderson <richard.henderson@linaro.org>
To: Ilya Leoshkevich <iii@linux.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PATCH] accel/tcg: Unmap perf_marker
Date: Mon, 5 Jun 2023 12:12:31 -0700 [thread overview]
Message-ID: <65849228-30b7-8b4d-605b-88973ba11a22@linaro.org> (raw)
In-Reply-To: <20230605114134.1169974-1-iii@linux.ibm.com>
On 6/5/23 04:41, Ilya Leoshkevich wrote:
> Coverity complains that perf_marker is never unmapped. Fix by unmapping
> it in perf_exit().
>
> Fixes: Coverity CID 1507929
> Fixes: 5584e2dbe8c9 ("tcg: add perfmap and jitdump")
> Signed-off-by: Ilya Leoshkevich<iii@linux.ibm.com>
> ---
> accel/tcg/perf.c | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
and applied to tcg-next.
r~
prev parent reply other threads:[~2023-06-05 19:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 11:41 [PATCH] accel/tcg: Unmap perf_marker Ilya Leoshkevich
2023-06-05 19:12 ` 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=65849228-30b7-8b4d-605b-88973ba11a22@linaro.org \
--to=richard.henderson@linaro.org \
--cc=iii@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).