From: "Alex Bennée" <alex.bennee@linaro.org>
To: Jayakrishnan A <jksoftdeveloper@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: Seeking help on implementing sync over ivshmem shared memory
Date: Tue, 25 Feb 2025 09:34:42 +0000 [thread overview]
Message-ID: <87ldtu74gd.fsf@draig.linaro.org> (raw)
In-Reply-To: <CAEHwtECacvmv98uAvXisx57qEN1hMbLjHNWUkm8mOt56wtWGaQ@mail.gmail.com> (Jayakrishnan A.'s message of "Sun, 23 Feb 2025 20:18:22 +0530")
Jayakrishnan A <jksoftdeveloper@gmail.com> writes:
> Hi Team ,
>
> Seeking help on implementing sync over ivshmem shared memory , As part of internal project we could able to achieve
> shared ivshmem with doorbell mechanism ,But in order to achieve shared memory synchronisation we are trying to add
> atomic operation over this shared memory area variables , Just wanted to analyse whether this atomic variable between
> VMs shared memory will work as expected , If not is there any suggested way ahead to implement synchronisation over
> ivshmem shared memory for threads running in multiple VMs.
Atomic accesses are properly modelled for all QEMU TCG guests that
support MTTCG using the hosts underlying atomic support. The shared
memory region ivshmem_bar2/server_bar2 are just pages shared between the
two QEMU processes so atomic accesses should behave the same way.
I'm unfamiliar with if both sides see the MMIO region but there is no
intrinsic synchronisation for MMIO regions which are terminated by a
MemoryRegionOps structure although vCPUS on the same QEMU will be
serialised by the BQL.
>
> Thanks and Regards ,
> Jayakrishnan A
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
prev parent reply other threads:[~2025-02-25 9:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-23 14:48 Seeking help on implementing sync over ivshmem shared memory Jayakrishnan A
2025-02-24 9:33 ` Philippe Mathieu-Daudé
2025-02-25 7:02 ` Jayakrishnan A
2025-02-25 9:34 ` Alex Bennée [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=87ldtu74gd.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=jksoftdeveloper@gmail.com \
--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).