All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Gustavo Romero <gustavo.romero@linaro.org>
Cc: qemu-devel@nongnu.org,  qemu-arm@nongnu.org,  philmd@linaro.org,
	alex.bennee@linaro.org,  thuth@redhat.com
Subject: Re: [RESEND][PATCH v3 0/7] Add ivshmem-flat device
Date: Tue, 07 Jan 2025 15:25:51 +0100	[thread overview]
Message-ID: <87r05e8zv4.fsf@pond.sub.org> (raw)
In-Reply-To: <20241216141818.111255-1-gustavo.romero@linaro.org> (Gustavo Romero's message of "Mon, 16 Dec 2024 14:18:11 +0000")

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

> This is a resend of the series:
>
> https://lore.kernel.org/qemu-devel/20240222222218.2261956-1-gustavo.romero@linaro.org/
>
> rebased on the current master. The series was sent about 9 months ago and
> remains relevant. Besides addressing the longstanding issue:
>
> https://gitlab.com/qemu-project/qemu/-/issues/1134
>
> it has generated interest in the community at least twice since its last
> version, from different contexts:
>
> https://lists.nongnu.org/archive/html/qemu-discuss/2024-05/msg00003.html
> https://lists.nongnu.org/archive/html/qemu-devel/2024-09/msg00374.html
>
> This suggests the series is being used out-of-tree in various contexts, such
> as experiments with heterogeneous architectures.
>
> But due to the fact it relies on sysbus, which is marked for future removal,
> some maintainers objected to accepting the patchset, causing it to be held in
> the ML.

Actually, I inquired about the use cases, and was told it's for OpenAMP.
I challenged the use of ivshmem for that purpose in some detail[*], but
got no reply.

>         However, given the ongoing community interest and since currently there
> isn't a better way on QEMU than using sysbus for the wiring needs of this
> device (e.g. to wire the device to a CPU IRQ input line), I'd kindly like to ask
> maintainers to reconsider its acceptance.



[*] https://lore.kernel.org/qemu-devel/87zfth4psf.fsf@pond.sub.org/

[...]

  parent reply	other threads:[~2025-01-07 14:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-16 14:18 [RESEND][PATCH v3 0/7] Add ivshmem-flat device Gustavo Romero
2024-12-16 14:18 ` [PATCH v3 1/7] hw/misc/ivshmem-flat: " Gustavo Romero
2024-12-31 18:01   ` Philippe Mathieu-Daudé
2024-12-31 19:10   ` Philippe Mathieu-Daudé
2024-12-16 14:18 ` [PATCH v3 2/7] hw/misc/ivshmem-flat: Allow device to wire itself on sysbus Gustavo Romero
2024-12-16 14:18 ` [PATCH v3 3/7] hw/arm: Allow some machines to use the ivshmem-flat device Gustavo Romero
2024-12-16 14:18 ` [PATCH v3 4/7] hw/misc/ivshmem: Rename ivshmem to ivshmem-pci Gustavo Romero
2024-12-16 14:18 ` [PATCH v3 5/7] tests/qtest: Reorganize common code in ivshmem-test Gustavo Romero
2024-12-16 14:18 ` [PATCH v3 6/7] tests/qtest: Add API functions to capture IRQ toggling Gustavo Romero
2025-01-07 18:35   ` Philippe Mathieu-Daudé
2025-01-07 18:57     ` Philippe Mathieu-Daudé
2024-12-16 14:18 ` [PATCH v3 7/7] tests/qtest: Add ivshmem-flat test Gustavo Romero
2025-01-07 14:25 ` Markus Armbruster [this message]
2025-01-07 17:02   ` [RESEND][PATCH v3 0/7] Add ivshmem-flat device 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=87r05e8zv4.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=gustavo.romero@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.