From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Jamie Iles <quic_jiles@quicinc.com>, qemu-devel@nongnu.org
Cc: richard.henderson@linaro.org, pbonzini@redhat.com,
peter.maydell@linaro.org
Subject: Re: [PATCH v3 1/2] cpu: expose qemu_cpu_list_lock for lock-guard use
Date: Sat, 29 Apr 2023 00:05:22 +0100 [thread overview]
Message-ID: <b80b77fc-71b7-9b83-1dd1-b371e0bda6d6@linaro.org> (raw)
In-Reply-To: <20230427020925.51003-2-quic_jiles@quicinc.com>
On 27/4/23 04:09, Jamie Iles wrote:
> Expose qemu_cpu_list_lock globally so that we can use
> WITH_QEMU_LOCK_GUARD and QEMU_LOCK_GUARD to simplify a few code paths
> now and in future.
>
> Signed-off-by: Jamie Iles <quic_jiles@quicinc.com>
> ---
> cpus-common.c | 2 +-
> include/exec/cpu-common.h | 1 +
> linux-user/elfload.c | 12 ++++++------
> migration/dirtyrate.c | 26 +++++++++++++-------------
> trace/control-target.c | 9 ++++-----
> 5 files changed, 25 insertions(+), 25 deletions(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2023-04-29 12:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 2:09 [PATCH v3 0/2] accel/tcg/tcg-accel-ops-rr: ensure fairness with icount Jamie Iles
2023-04-27 2:09 ` [PATCH v3 1/2] cpu: expose qemu_cpu_list_lock for lock-guard use Jamie Iles
2023-04-27 7:44 ` Richard Henderson
2023-04-28 23:05 ` Philippe Mathieu-Daudé [this message]
2023-04-27 2:09 ` [PATCH v3 2/2] accel/tcg/tcg-accel-ops-rr: ensure fairness with icount Jamie Iles
2023-04-27 7:46 ` Richard Henderson
2023-04-29 9:28 ` [PATCH v3 0/2] " Richard Henderson
2023-04-29 12:23 ` Philippe Mathieu-Daudé
2023-05-03 9:44 ` Jamie Iles
2023-05-10 15:01 ` 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=b80b77fc-71b7-9b83-1dd1-b371e0bda6d6@linaro.org \
--to=philmd@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quic_jiles@quicinc.com \
--cc=richard.henderson@linaro.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).