From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: ankita suman <ankita.suman7@gmail.com>, qemu-discuss@nongnu.org
Cc: Gustavo Romero <gustavo.romero@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
qemu-arm <qemu-arm@nongnu.org>
Subject: Re: Emulating multi core processor (ARM cortex M7) on QEMU
Date: Mon, 26 Feb 2024 12:09:55 +0100 [thread overview]
Message-ID: <4f8f7404-977d-4ff2-8987-a704bb260244@linaro.org> (raw)
In-Reply-To: <CAJSdhPiUcGuHmtZbgaN3Op5qqyDGacN1s9DeGJkmQrx6HL19VQ@mail.gmail.com>
Hello,
On 26/2/24 11:58, ankita suman wrote:
> Hello,
>
> I am trying to emulate multi core processor (dual core for now) on QEMU.
> The processor I am targeting is cortex m7. I tried by running multiple
> instances of QEMU to emulate multi cores, and use shared memory for
> communication, but since I am working on a bare metal environment, I
> don't have the options of libraries for synchronization.
Have a look at the 'fby35' machine in hw/arm/fby35.c, it uses
a pair of Aspeed ast1030 and ast2600 ARM cores.
> Another approach I tried was using inter VM shared memory(ivshmem). But
> I am facing the same problem. I am able to write and read from the
> ivshmem device from two different QEMU instances, but it is not working
> for ARM.
Cc'ing Gustavo who worked on something similar and posted ivshmem
patches:
https://lore.kernel.org/qemu-devel/20240222222218.2261956-1-gustavo.romero@linaro.org/
> can someone please guide me on how to proceed and what is the best
> approach? If there are library support in QEMU for multi core emulation,
> kindly let me know, that would be helpful as well.
Regards,
Phil.
parent reply other threads:[~2024-02-26 11:11 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAJSdhPiUcGuHmtZbgaN3Op5qqyDGacN1s9DeGJkmQrx6HL19VQ@mail.gmail.com>]
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=4f8f7404-977d-4ff2-8987-a704bb260244@linaro.org \
--to=philmd@linaro.org \
--cc=ankita.suman7@gmail.com \
--cc=gustavo.romero@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@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).