From: Andrew Jones <drjones@redhat.com>
To: Anup Patel <anup@brainfault.org>
Cc: qemu-devel@nongnu.org,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>
Subject: Re: [Qemu-devel] [PATCH] virtio: Introduce virtio-testdev
Date: Tue, 15 Oct 2013 10:36:19 +0200 [thread overview]
Message-ID: <20131015083618.GA2181@hawk.usersys.redhat.com> (raw)
In-Reply-To: <CAAhSdy0v5uV11DgSDsKcRDq-jEqK=n6GZGGR+iUzY8Y9RqwJKg@mail.gmail.com>
On Tue, Oct 15, 2013 at 12:26:10PM +0530, Anup Patel wrote:
> Hi Andrew,
>
> On Mon, Oct 14, 2013 at 9:29 PM, Andrew Jones <drjones@redhat.com> wrote:
> > This is a virtio version of hw/misc/debugexit and should evolve into a
> > virtio version of pc-testdev. pc-testdev uses the PC's ISA bus, whereas
> > this testdev can be plugged into a virtio-mmio transport, which is
> > needed for kvm-unit-tests/arm. virtio-testdev uses the virtio device
> > config space as a communication channel, and implements an RTAS-like
> > protocol through it allowing guests to execute commands. Only three
> > commands are currently implemented;
> > 1) VERSION: for version compatibility checks
> > 2) CLEAR: set all the config space back to zero
> > 3) EXIT: exit() from qemu with a status code
>
> How about adding RESET command to reset the VM?
>
Hi Anup,
I'm not opposed to it, but at the moment I'm not sure how we would
utilize it within kvm-unit-tests. Maybe it would be useful for another
application though? So maybe we can add it as an add-on patch at the
time we come up with its use case?
Thanks for the review!
drew
next prev parent reply other threads:[~2013-10-15 8:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 15:59 [Qemu-devel] [PATCH] virtio: Introduce virtio-testdev Andrew Jones
2013-10-15 6:56 ` Anup Patel
2013-10-15 8:36 ` Andrew Jones [this message]
2013-10-15 9:47 ` Anup Patel
2013-10-15 9:51 ` Anup Patel
2013-10-15 10:14 ` Peter Maydell
2013-10-15 10:38 ` Gleb Natapov
2013-10-15 10:50 ` Anup Patel
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=20131015083618.GA2181@hawk.usersys.redhat.com \
--to=drjones@redhat.com \
--cc=anup@brainfault.org \
--cc=kvmarm@lists.cs.columbia.edu \
--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).