From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Harsh Prateek Bora" <harshpb@linux.ibm.com>,
<qemu-ppc@nongnu.org>, <qemu-devel@nongnu.org>
Cc: <danielhb413@gmail.com>, <vaibhav@linux.ibm.com>, <sbhat@linux.ibm.com>
Subject: Re: [PATCH v3 2/3] cpu-common.c: export cpu_get_free_index to be reused later
Date: Thu, 30 May 2024 18:32:32 +1000 [thread overview]
Message-ID: <D1MU8TS7UZ4U.2R3WBGRCIANZD@gmail.com> (raw)
In-Reply-To: <20240523072614.256172-3-harshpb@linux.ibm.com>
On Thu May 23, 2024 at 5:26 PM AEST, Harsh Prateek Bora wrote:
> This helper provides an easy way to identify the next available free cpu
> index which can be used for vcpu creation. Until now, this is being
> called at a very later stage and there is a need to be able to call it
> earlier (for now, with ppc64) hence the need to export.
>
Reviewed-by: Nicholas Piggin <npiggin@gmail.com>
> Suggested-by: Nicholas Piggin <npiggin@gmail.com>
> Signed-off-by: Harsh Prateek Bora <harshpb@linux.ibm.com>
> ---
> include/exec/cpu-common.h | 2 ++
> cpu-common.c | 7 ++++---
> 2 files changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/include/exec/cpu-common.h b/include/exec/cpu-common.h
> index 6d5318895a..0386f1ab29 100644
> --- a/include/exec/cpu-common.h
> +++ b/include/exec/cpu-common.h
> @@ -29,6 +29,8 @@ void cpu_list_lock(void);
> void cpu_list_unlock(void);
> unsigned int cpu_list_generation_id_get(void);
>
> +int cpu_get_free_index(void);
> +
> void tcg_iommu_init_notifier_list(CPUState *cpu);
> void tcg_iommu_free_notifier_list(CPUState *cpu);
>
> diff --git a/cpu-common.c b/cpu-common.c
> index ce78273af5..82bd1b432d 100644
> --- a/cpu-common.c
> +++ b/cpu-common.c
> @@ -57,14 +57,12 @@ void cpu_list_unlock(void)
> qemu_mutex_unlock(&qemu_cpu_list_lock);
> }
>
> -static bool cpu_index_auto_assigned;
>
> -static int cpu_get_free_index(void)
> +int cpu_get_free_index(void)
> {
> CPUState *some_cpu;
> int max_cpu_index = 0;
>
> - cpu_index_auto_assigned = true;
> CPU_FOREACH(some_cpu) {
> if (some_cpu->cpu_index >= max_cpu_index) {
> max_cpu_index = some_cpu->cpu_index + 1;
> @@ -83,8 +81,11 @@ unsigned int cpu_list_generation_id_get(void)
>
> void cpu_list_add(CPUState *cpu)
> {
> + static bool cpu_index_auto_assigned;
> +
> QEMU_LOCK_GUARD(&qemu_cpu_list_lock);
> if (cpu->cpu_index == UNASSIGNED_CPU_INDEX) {
> + cpu_index_auto_assigned = true;
> cpu->cpu_index = cpu_get_free_index();
> assert(cpu->cpu_index != UNASSIGNED_CPU_INDEX);
> } else {
next prev parent reply other threads:[~2024-05-30 8:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 7:26 [PATCH v3 0/3] target/ppc: vcpu hotplug failure handling fixes Harsh Prateek Bora
2024-05-23 7:26 ` [PATCH v3 1/3] accel/kvm: Introduce kvm_create_and_park_vcpu() helper Harsh Prateek Bora
2024-05-30 8:31 ` Nicholas Piggin
2024-05-23 7:26 ` [PATCH v3 2/3] cpu-common.c: export cpu_get_free_index to be reused later Harsh Prateek Bora
2024-05-30 8:32 ` Nicholas Piggin [this message]
2024-05-23 7:26 ` [PATCH v3 3/3] target/ppc: handle vcpu hotplug failure gracefully Harsh Prateek Bora
2024-05-30 8:38 ` Nicholas Piggin
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=D1MU8TS7UZ4U.2R3WBGRCIANZD@gmail.com \
--to=npiggin@gmail.com \
--cc=danielhb413@gmail.com \
--cc=harshpb@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=sbhat@linux.ibm.com \
--cc=vaibhav@linux.ibm.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).