From: Andrew Jones <drjones@redhat.com>
To: Mike Day <ncmike@ncultra.org>
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org,
christoffer.dall@linaro.org, kvmarm@lists.cs.columbia.edu
Subject: Re: [Qemu-devel] [PATCH v3] virtio: Introduce virtio-testdev
Date: Thu, 30 Jan 2014 13:56:52 +0100 [thread overview]
Message-ID: <20140130125651.GA5748@hawk.usersys.redhat.com> (raw)
In-Reply-To: <87mwidvdtg.fsf@pixel.localdomain>
On Thu, Jan 30, 2014 at 07:44:59AM -0500, Mike Day wrote:
>
> Andrew Jones <drjones@redhat.com> writes:
>
> > 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
>
> > +static uint32_t virtio_testdev_get_features(VirtIODevice *vdev, uint32_t f)
> > +{
> > + return f;
> > +}
> > +
>
> Is this meant to be a stub currently?
>
Something like that. *_get_features() must be supplied by all virtio
devices. Just returning the requested features, f, rather than zero,
is how virtio-rng does it. So I went that way too.
drew
prev parent reply other threads:[~2014-01-30 12:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 15:19 [Qemu-devel] [PATCH v3] virtio: Introduce virtio-testdev Andrew Jones
2014-01-30 12:44 ` Mike Day
2014-01-30 12:56 ` Andrew Jones [this message]
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=20140130125651.GA5748@hawk.usersys.redhat.com \
--to=drjones@redhat.com \
--cc=christoffer.dall@linaro.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=ncmike@ncultra.org \
--cc=peter.maydell@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.