"Edgar E. Iglesias" <edgar.igles...@gmail.com> writes:
> Hi,
>
> I would like to use qtest for testing hw-models in combination with firmware.
>
> At the moment I'm using the following patch to allow qtest to run without
> accel=qtest. I'm mostly interested in the mem access functions and the
> interrupt interception. I guess time stepping wouldnt work without
> accel=qtest, but maybe that could be an acceptable limitation.
>
> Is there anything in principle with such a setup that would cause
> problems?
Interesting. No, I can't think of any problems in principle with doing
this. It was not a use case I had considered.
Regards,
Anthony Liguori
>
> Thanks,
> Edgar
>
>
> commit 947414a56e256139a510a034c02ac277ad577272
> Author: Edgar E. Iglesias <edgar.igles...@gmail.com>
> Date: Wed Apr 10 20:32:17 2013 +0200
>
> Allow qtest to be used together with a virtual CPU
>
> Signed-off-by: Edgar E. Iglesias <edgar.igles...@gmail.com>
>
> diff --git a/vl.c b/vl.c
> index c566caf..0dbac29 100644
> --- a/vl.c
> +++ b/vl.c
> @@ -4143,6 +4143,10 @@ int main(int argc, char **argv, char **envp)
>
> configure_accelerator();
>
> + if (!qtest_enabled() && qtest_chrdev) {
> + qtest_init();
> + }
> +
> machine_opts = qemu_opts_find(qemu_find_opts("machine"), 0);
> if (machine_opts) {
> kernel_filename = qemu_opt_get(machine_opts, "kernel");
