[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 0/3] implement a new icount_no_rt mode

From: Victor Clement
Subject: Re: [Qemu-devel] [PATCH 0/3] implement a new icount_no_rt mode
Date: Fri, 29 May 2015 10:54:13 +0200 (CEST)

----- Mail original -----
> De: "Paolo Bonzini" <address@hidden>
> À: "Victor CLEMENT" <address@hidden>, address@hidden
> Cc: "francois guerret" <address@hidden>
> Envoyé: Mercredi 27 Mai 2015 14:52:55
> Objet: Re: [Qemu-devel] [PATCH 0/3] implement a new icount_no_rt mode
> [...] Or are there other cases besides RTC devices?
> Paolo

For the normal use case of QEmu, No. But we want to use QEmu to test hard
real time application against simulated external stimuli.

So basically, Qemu will be used to run the embedded software, but
the external interfaces (GPIO, SPI, CAN bus...) will be controlled
by a basic simulator playing some predefined scenario.
Also we will record some traces to validate the behavior.

The scenario engine and the trace recorder will need to use the virtual
clock, so that all dates are based on the same clock.

Again, at this stage we think this scenario engine will not be generic
so the code will not be ready for integration in qemu.

Our goal is to be able to run a real time application (under an RTOS)
and test it with some scenario :
For instance our application could monitor a GPIO and send a specific
CAN frame within a specified delay.
In that case, the scenario will control the GPIO input and the recorder
will trace both the GPIO and the CAN bus. So by analysing the traces
we will be able to check that the software meets its timing constraints.

This example is simple but still shows the kind of problems we want to

I hope this enlighten you on our motivations.

Best regards,

Victor Clément & Julien Viard de Galbert

reply via email to

[Prev in Thread] Current Thread [Next in Thread]