Re: QEMU Library support

[Pratik Parvati <pratikp@vayavyalabs.com>]

[-- Attachment #1: Type: text/plain, Size: 2374 bytes --]

Just to hide the core QEMU implementation from the device code. QEMU core
source code remains the same for all device; So, was thinking a way of
hiding it from the rest of the device code.

Regards,
Pratik


On Mon, Aug 10, 2020 at 3:50 PM Alex Bennée <alex.bennee@linaro.org> wrote:

>
> Pratik Parvati <pratikp@vayavyalabs.com> writes:
>
> > As an experiment, I have modelled non-existing ARM Watchdog model (SP805)
> > interfaced to the versatile PB platform. What actually I was looking is -
> > some sort of QEMU library, where I can model new device outside the QEMU
> > source hierarchy and still be able to compile it using QEMU library and
> > include files to add support for the new device. If QEMU doesn't provide
> a
> > library, Is there a flexibly that I can tweak something inside the QEMU
> to
> > generate it?
>
> Not really. While most devices are fairly standalone they can access all
> sorts of QEMU APIs. Why not just implement your device inside the QEMU
> source tree?
>
> >
> > Regards,
> > Pratik
> >
> >
> > On Mon, Aug 10, 2020 at 3:18 PM Alex Bennée <alex.bennee@linaro.org>
> wrote:
> >
> >>
> >> Pratik Parvati <pratikp@vayavyalabs.com> writes:
> >>
> >> > Hi team,
> >> >
> >> > Lately, I have been working on QEMU modeling and interfacing it into
> the
> >> > existing platform. What actually I wanted to check is; whether QEMU
> >> > supports library that gives developers a clean interface to develop
> and
> >> > integrate peripheral model in to QEMU. I know of the Greensocs SystemC
> >> > bridge - but that was quite difficult to work with in past.
> >>
> >> Not really - with a few exceptions like vhost-user and in KVM device
> >> emulation all devices are emulated in the QEMU code base. As a result
> >> the best way to maintain a device is to have it integrated upstream
> >> (along with some tests to ensure it is working).
> >>
> >> As you note there are various forks of QEMU that support device
> >> modelling but none of these features have been merged upstream and would
> >> likely need to assuage worries about such interfaces being used to avoid
> >> GPL compliance.
> >>
> >> What sort of devices are you looking to model? Are these existing
> >> devices or experimental/research things?
> >>
> >> --
> >> Alex Bennée
> >>
>
>
> --
> Alex Bennée
>

[-- Attachment #2: Type: text/html, Size: 3319 bytes --]