From: Richard Henderson <richard.henderson@linaro.org>
To: Jamie Iles <quic_jiles@quicinc.com>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: [PATCH v2] accel/tcg/tcg-accel-ops-rr: ensure fairness with icount
Date: Mon, 24 Apr 2023 14:06:18 +0100 [thread overview]
Message-ID: <e612395f-ade3-6ceb-a611-8c9c41caeb31@linaro.org> (raw)
In-Reply-To: <20230424112907.26832-1-quic_jiles@quicinc.com>
On 4/24/23 12:29, Jamie Iles wrote:
> +/*
> + * Calculate the number of CPUs that we will process in a single iteration of
> + * the main CPU thread loop so that we can fairly distribute the instruction
> + * count across CPUs.
> + *
> + * The CPU count is cached based on the CPU list generation ID to avoid
> + * iterating the list every time.
> + */
> +static int rr_cpu_count(void)
> +{
> + static unsigned int last_gen_id = ~0;
> + static int cpu_count;
> + CPUState *cpu;
> +
> + cpu_list_lock();
> + if (cpu_list_generation_id_get() != last_gen_id) {
> + cpu_count = 0;
> + CPU_FOREACH(cpu) {
> + ++cpu_count;
> + }
> + last_gen_id = cpu_list_generation_id_get();
> + }
> + cpu_list_unlock();
> +
> + return cpu_count;
> +}
The read of cpu_count should be in the lock.
(Ideally we'd expose QEMU_LOCK_GUARD(&qemu_cpu_list_lock) which would make the read+return
trivial.)
> /*
> * In the single-threaded case each vCPU is simulated in turn. If
> * there is more than a single vCPU we create a simple timer to kick
> @@ -185,6 +212,9 @@ static void *rr_cpu_thread_fn(void *arg)
> cpu->exit_request = 1;
>
> while (1) {
> + int cpu_count = rr_cpu_count();
> + int64_t cpu_budget = INT64_MAX;
> +
> qemu_mutex_unlock_iothread();
> replay_mutex_lock();
> qemu_mutex_lock_iothread();
> @@ -197,6 +227,8 @@ static void *rr_cpu_thread_fn(void *arg)
> * waking up the I/O thread and waiting for completion.
> */
> icount_handle_deadline();
> +
> + cpu_budget = icount_percpu_budget(cpu_count);
I think you can move the call to rr_cpu_count() here, so that it only happens if icount is
in use.
Why cpu_budget = INT64_MAX as opposed to 0 or 0xdeadbeef? It's not set or used except for
icount_enabled.
r~
next prev parent reply other threads:[~2023-04-24 13:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 11:29 [PATCH v2] accel/tcg/tcg-accel-ops-rr: ensure fairness with icount Jamie Iles
2023-04-24 13:06 ` Richard Henderson [this message]
2023-04-24 13:21 ` Jamie Iles
2023-04-24 13:26 ` 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=e612395f-ade3-6ceb-a611-8c9c41caeb31@linaro.org \
--to=richard.henderson@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quic_jiles@quicinc.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).