From: Andrew Jones <andrew.jones@linux.dev>
To: kvm@vger.kernel.org, kvm-riscv@lists.infradead.org,
kvmarm@lists.linux.dev
Cc: atishp@rivosinc.com, jamestiotio@gmail.com,
alexandru.elisei@arm.com, eric.auger@redhat.com
Subject: Re: [kvm-unit-tests PATCH v2 2/3] lib/on-cpus: Add barrier after func call
Date: Wed, 6 Nov 2024 09:15:35 +0100 [thread overview]
Message-ID: <20241106-9611aa66dfd52197b3b00e96@orel> (raw)
In-Reply-To: <20241031123948.320652-7-andrew.jones@linux.dev>
On Thu, Oct 31, 2024 at 01:39:51PM +0100, Andrew Jones wrote:
> It's reasonable for users of on_cpu() and on_cpumask() to assume
> they can read data that 'func' has written when the call completes.
> Ensure the caller doesn't observe a completion (target cpus are again
> idle) without also being able to observe any writes which were made
> by func(). Do so by adding barriers to implement the following
>
> target-cpu calling-cpu
> ---------- -----------
> func() /* store something */ /* wait for target to be idle */
> smp_wmb(); smp_rmb();
> set_cpu_idle(smp_processor_id(), true); /* load what func() stored */
>
> Signed-off-by: Andrew Jones <andrew.jones@linux.dev>
I added a
Suggested-by: Alexandru Elisei <alexandru.elisei@arm.com>
to this patch.
> ---
> lib/on-cpus.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/lib/on-cpus.c b/lib/on-cpus.c
> index f6072117fa1b..356f284be61b 100644
> --- a/lib/on-cpus.c
> +++ b/lib/on-cpus.c
> @@ -79,6 +79,7 @@ void do_idle(void)
> smp_wait_for_event();
> smp_rmb();
> on_cpu_info[cpu].func(on_cpu_info[cpu].data);
> + smp_wmb(); /* pairs with the smp_rmb() in on_cpu() and on_cpumask() */
> }
> }
>
> @@ -145,12 +146,14 @@ void on_cpumask(const cpumask_t *mask, void (*func)(void *data), void *data)
> smp_wait_for_event();
> for_each_cpu(cpu, mask)
> cpumask_clear_cpu(me, &on_cpu_info[cpu].waiters);
> + smp_rmb(); /* pairs with the smp_wmb() in do_idle() */
> }
>
> void on_cpu(int cpu, void (*func)(void *data), void *data)
> {
> on_cpu_async(cpu, func, data);
> cpu_wait(cpu);
> + smp_rmb(); /* pairs with the smp_wmb() in do_idle() */
> }
>
> void on_cpus(void (*func)(void *data), void *data)
> --
> 2.47.0
>
>
> --
> kvm-riscv mailing list
> kvm-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kvm-riscv
next prev parent reply other threads:[~2024-11-06 8:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 12:39 [kvm-unit-tests PATCH v2 0/3] lib/on-cpus: A couple of fixes Andrew Jones
2024-10-31 12:39 ` [kvm-unit-tests PATCH v2 1/3] lib/on-cpus: Correct and simplify synchronization Andrew Jones
2024-11-07 10:01 ` Eric Auger
2024-10-31 12:39 ` [kvm-unit-tests PATCH v2 2/3] lib/on-cpus: Add barrier after func call Andrew Jones
2024-11-06 8:15 ` Andrew Jones [this message]
2024-11-07 10:02 ` Eric Auger
2024-10-31 12:39 ` [kvm-unit-tests PATCH v2 3/3] lib/on-cpus: Fix on_cpumask Andrew Jones
2024-11-07 17:55 ` Eric Auger
2024-11-11 14:36 ` [kvm-unit-tests PATCH v2 0/3] lib/on-cpus: A couple of fixes Andrew Jones
2024-12-03 11:43 ` Alexandru Elisei
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=20241106-9611aa66dfd52197b3b00e96@orel \
--to=andrew.jones@linux.dev \
--cc=alexandru.elisei@arm.com \
--cc=atishp@rivosinc.com \
--cc=eric.auger@redhat.com \
--cc=jamestiotio@gmail.com \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
/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