From: Jayakrishnan A <jksoftdeveloper@gmail.com>
To: qemu-devel@nongnu.org
Subject: Seeking help on implementing sync over ivshmem shared memory
Date: Sun, 23 Feb 2025 20:18:22 +0530 [thread overview]
Message-ID: <CAEHwtECacvmv98uAvXisx57qEN1hMbLjHNWUkm8mOt56wtWGaQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 573 bytes --]
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.
Thanks and Regards ,
Jayakrishnan A
[-- Attachment #2: Type: text/html, Size: 716 bytes --]
next reply other threads:[~2025-02-23 15:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-23 14:48 Jayakrishnan A [this message]
2025-02-24 9:33 ` Seeking help on implementing sync over ivshmem shared memory Philippe Mathieu-Daudé
2025-02-25 7:02 ` Jayakrishnan A
2025-02-25 9:34 ` Alex Bennée
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=CAEHwtECacvmv98uAvXisx57qEN1hMbLjHNWUkm8mOt56wtWGaQ@mail.gmail.com \
--to=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).