qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Gustavo Romero <gustavo.romero@linaro.org>
Cc: qemu-devel@nongnu.org,  philmd@linaro.org,
	 peter.maydell@linaro.org, richard.henderson@linaro.org,
	 thuth@redhat.com
Subject: Re: [PATCH 0/4] Add ivshmem-flat device
Date: Tue, 19 Dec 2023 16:21:47 +0000	[thread overview]
Message-ID: <87wmta2mec.fsf@draig.linaro.org> (raw)
In-Reply-To: <20231127052024.435743-1-gustavo.romero@linaro.org> (Gustavo Romero's message of "Mon, 27 Nov 2023 05:20:20 +0000")

Gustavo Romero <gustavo.romero@linaro.org> writes:

> This patchset introduces a new device, ivshmem-flat, which is similar to the
> current ivshmem device but does not require a PCI bus. It implements the ivshmem
> status and control registers as MMRs and the shared memory as a directly
> accessible memory region in the VM memory layout. It's meant to be used on
> machines like those with Cortex-M MCUs, which usually lack a PCI bus, e.g.,
> lm3s6965evb and mps2-an385. Additionally, it has the benefit of requiring a tiny
> 'device driver,' which is helpful on some RTOSes, like Zephyr, that run on
> memory-constrained resource targets.
>
> The patchset includes a QTest for the ivshmem-flat device, however, it's also
> possible to experiment with it in two ways:
>
> (a) using two Cortex-M VMs running Zephyr; or
> (b) using one aarch64 VM running Linux with the ivshmem PCI device and another
>     arm (Cortex-M) VM running Zephyr with the new ivshmem-flat device.
>
> Please note that for running the ivshmem-flat QTests the following patch, which
> is not committed to the tree yet, must be applied:
>
> https://lists.nongnu.org/archive/html/qemu-devel/2023-11/msg03176.html
>
> --
>
> To experiment with (a), clone this Zephyr repo [0], set the Zephyr build
> environment [1], and follow the instructions in the 'ivshmem' sample main.c [2].
>
> [0] https://github.com/gromero/zephyr/tree/ivshmem
> [1] https://docs.zephyrproject.org/latest/develop/getting_started/index.html
> [2] https://github.com/gromero/zephyr/commit/73fbd481e352b25ae5483ba5048a2182b90b7f00#diff-16fa1f481a49b995d0d1a62da37b9f33033f5ee477035e73465e7208521ddbe0R9-R70
>
> To experiment with (b):

If you could put these blobs up on fileserver.linaro.org you could add
an avocado test to compliment the qtest.

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


      parent reply	other threads:[~2023-12-19 16:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27  5:20 [PATCH 0/4] Add ivshmem-flat device Gustavo Romero
2023-11-27  5:20 ` [PATCH 1/4] " Gustavo Romero
2023-11-29 18:19   ` Philippe Mathieu-Daudé
2024-02-16 13:14   ` Philippe Mathieu-Daudé
2023-11-27  5:20 ` [PATCH 2/4] tests/qtest: Reorganize common code in ivshmem-test Gustavo Romero
2024-02-13 15:56   ` Philippe Mathieu-Daudé
2023-11-27  5:20 ` [PATCH 3/4] tests/qtest: Add ivshmem-flat test Gustavo Romero
2023-11-27  5:20 ` [PATCH 4/4] hw/misc/ivshmem: Rename ivshmem to ivshmem-pci Gustavo Romero
2023-11-29 18:20   ` Philippe Mathieu-Daudé
2023-12-19 16:21 ` 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=87wmta2mec.fsf@draig.linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=gustavo.romero@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=thuth@redhat.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).