From: Anthony Liguori <anthony@codemonkey.ws>
To: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] QTest with TCG?
Date: Mon, 15 Apr 2013 14:03:57 -0500 [thread overview]
Message-ID: <87li8jsjj6.fsf@codemonkey.ws> (raw)
In-Reply-To: <20130415182358.GF26210@smtp.vpn>
"Edgar E. Iglesias" <edgar.iglesias@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.iglesias@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.iglesias@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");
next prev parent reply other threads:[~2013-04-15 19:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 18:23 [Qemu-devel] QTest with TCG? Edgar E. Iglesias
2013-04-15 19:03 ` Anthony Liguori [this message]
2013-04-16 5:11 ` Paolo Bonzini
2013-04-16 7:48 ` Edgar E. Iglesias
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=87li8jsjj6.fsf@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=edgar.iglesias@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).