From: Markus Armbruster <armbru@redhat.com>
To: Ruslan Ruslichenko <ruslichenko.r@gmail.com>
Cc: qemu-devel@nongnu.org, qemu-arm@nongnu.org,
artem_mygaiev@epam.com, takahiro.nakata.wr@renesas.com,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: Question on preferred location for QEMU sample projects
Date: Thu, 30 Apr 2026 06:48:17 +0200 [thread overview]
Message-ID: <875x59vysu.fsf@pond.sub.org> (raw)
In-Reply-To: <CAN-aV1HDZfoJv3OCm9_f3epNtvvr5CrvB-1Fi4y7jGLwF3Xx7g@mail.gmail.com> (Ruslan Ruslichenko's message of "Wed, 29 Apr 2026 21:25:21 +0200")
Ruslan Ruslichenko <ruslichenko.r@gmail.com> writes:
> On Mon, Apr 13, 2026 at 4:04 PM Ruslan Ruslichenko
> <ruslichenko.r@gmail.com> wrote:
>>
>> On Mon, Apr 13, 2026 at 9:25 AM Markus Armbruster <armbru@redhat.com> wrote:
>> >
>> > Ruslan Ruslichenko <ruslichenko.r@gmail.com> writes:
>> >
>> > > Hi everyone,
>> > >
>> > > We are currently preparing the v2 patch series for the Remote-Port
>> > > Co-simulation protocol for interfacing with SystemC modules. The first
>> > > revision was here:
>> > > https://lists.nongnu.org/archive/html/qemu-devel/2026-02/msg01760.html.
>> > >
>> > > As part of this submission, we would like to publish a sample project
>> > > serving as a demonstration of how to connect a QEMU Remote-Port
>> > > frontend to a SystemC backend.
>> > >
>> > > The sample project implements a standard SystemC IP core and uses
>> > > several external components such as:
>> > > - libsystemctlm-soc: https://github.com/Xilinx/libsystemctlm-soc
>> > > - VCML Library: https://github.com/machineware-gmbh/vcml
>> > > - SystemC Library: https://github.com/accellera-official/systemc
>> > >
>> > > We have a question regarding the location for this kind of project.
>> > > Could you please suggest if there is a preferred location or some
>> > > standard practice for hosting such a sample project?
>> >
>> > Location within the QEMU source tree?
>> >
>>
>> Hello Markus,
>>
>> Yes, it would be good to include this project within the QEMU source tree.
>> To build the project, the mentioned SystemC, libsystemctlm-soc and
>> VCML libraries and their specific dependencies need to be built and
>> installed separately.
>> Would this approach be acceptable?
We have a few (small) examples under contrib/. However, Peter (cc'ed)
has been trying to clean out that directory.
>>
>> Alternatively, is there an auxiliary repository within the QEMU
>> infrastructure that is better suited for these types of sample
>> projects,
>> perhaps somewhere under https://gitlab.com/qemu-project?
>>
>> --
>> BR,
>> Ruslan
>
> Hello Markus,
>
> Do you have any thoughts on the preferred location for this sample project?
>
> Best regards,
> Ruslan
Peter, what about you?
next prev parent reply other threads:[~2026-04-30 4:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 14:39 Question on preferred location for QEMU sample projects Ruslan Ruslichenko
2026-04-13 7:24 ` Markus Armbruster
2026-04-13 14:04 ` Ruslan Ruslichenko
2026-04-29 19:25 ` Ruslan Ruslichenko
2026-04-30 4:48 ` Markus Armbruster [this message]
2026-04-30 8:45 ` Peter Maydell
2026-04-30 8:01 ` Daniel P. Berrangé
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=875x59vysu.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=artem_mygaiev@epam.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=ruslichenko.r@gmail.com \
--cc=takahiro.nakata.wr@renesas.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.