From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
qemu-devel@nongnu.org, stratos-dev@op-lists.linaro.org
Subject: Re: [PATCH 0/2] virtio: Add vhost-user-gpio device's support
Date: Thu, 20 Jan 2022 15:41:57 +0000 [thread overview]
Message-ID: <87ilue75zv.fsf@linaro.org> (raw)
In-Reply-To: <20220120055543-mutt-send-email-mst@kernel.org>
"Michael S. Tsirkin" <mst@redhat.com> writes:
> On Thu, Jan 20, 2022 at 09:32:34AM +0530, Viresh Kumar wrote:
>> On 17-01-22, 10:11, Alex Bennée wrote:
>> >
>> > "Michael S. Tsirkin" <mst@redhat.com> writes:
>> >
>> > > On Wed, Jan 12, 2022 at 05:04:57PM +0530, Viresh Kumar wrote:
>> > >> Hello,
>> > >>
>> > >> This patchset adds vhost-user-gpio device's support in Qemu. The support for the
>> > >> same has already been added to virtio specification and Linux Kernel.
>> > >>
>> > >> A Rust based backend is also in progress and is tested against this patchset:
>> > >>
>> > >> https://github.com/rust-vmm/vhost-device/pull/76
>> > >
>> > >
>> > > I'm reluctant to add this with no tests in tree.
>> > > Want to write a minimal libhost-user based backend?
>>
>> I actually have one already, that I wrote before attempting the Rust
>> counterpart, but never upstreamed as I am not sure if anyone is ever
>> going to use it, as I am not. And I thought what's the point of
>> merging code which I will never end up using.
>>
>> I am not sure what test I can add here to make sure this doesn't
>> breaks in future though.
>
> something that executes with make check.
With Eric's latest series
(20220118203833.316741-1-eric.auger@redhat.com) we are already
exercising most of the PCI code:
➜ gcov ./libqemu-aarch64-softmmu.fa.p/hw_virtio_vhost-user-gpio.c.gcda
File '../../hw/virtio/vhost-user-gpio.c'
Lines executed:10.43% of 163
Creating 'vhost-user-gpio.c.gcov'
File '/home/alex/lsrc/qemu.git/include/qemu/bitops.h'
Lines executed:100.00% of 4
Creating 'bitops.h.gcov'
File '/home/alex/lsrc/qemu.git/include/hw/virtio/virtio.h'
Lines executed:12.50% of 8
Creating 'virtio.h.gcov'
File '/home/alex/lsrc/qemu.git/include/hw/virtio/vhost-user-gpio.h'
Lines executed:0.00% of 1
Creating 'vhost-user-gpio.h.gcov'
File '/home/alex/lsrc/qemu.git/include/hw/virtio/virtio-bus.h'
Lines executed:0.00% of 1
Creating 'virtio-bus.h.gcov'
File '/home/alex/lsrc/qemu.git/include/hw/qdev-core.h'
Lines executed:50.00% of 2
Creating 'qdev-core.h.gcov'
🕙15:40:35 alex@zen:qemu.git/builds/gprof on review/virtio-gpio-boilerplate [$?]
➜ gcov ./libqemu-aarch64-softmmu.fa.p/hw_virtio_vhost-user-gpio-pci.c.gcda
File '../../hw/virtio/vhost-user-gpio-pci.c'
Lines executed:76.92% of 26
Creating 'vhost-user-gpio-pci.c.gcov'
File '/home/alex/lsrc/qemu.git/include/qemu/bitops.h'
Lines executed:100.00% of 4
Creating 'bitops.h.gcov'
File '../../hw/virtio/virtio-pci.h'
Lines executed:100.00% of 1
Creating 'virtio-pci.h.gcov'
File '/home/alex/lsrc/qemu.git/include/hw/pci/pci.h'
Lines executed:100.00% of 1
Creating 'pci.h.gcov'
File '/home/alex/lsrc/qemu.git/include/hw/qdev-core.h'
Lines executed:50.00% of 2
Creating 'qdev-core.h.gcov'
So I think if we add the runes to ensure we instantiate both types
explicitly I think we will have enough coverage.
--
Alex Bennée
next prev parent reply other threads:[~2022-01-20 21:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 11:34 [PATCH 0/2] virtio: Add vhost-user-gpio device's support Viresh Kumar
2022-01-12 11:34 ` [PATCH 1/2] hw/virtio: add boilerplate for vhost-user-gpio device Viresh Kumar
2022-01-14 14:05 ` Alex Bennée
2022-01-14 14:06 ` Alex Bennée
2022-01-17 6:38 ` Viresh Kumar
2022-01-17 10:17 ` Alex Bennée
2022-01-12 11:34 ` [PATCH 2/2] hw/virtio: add vhost-user-gpio-pci boilerplate Viresh Kumar
2022-01-14 14:10 ` Alex Bennée
2022-01-17 8:47 ` [PATCH 0/2] virtio: Add vhost-user-gpio device's support Michael S. Tsirkin
2022-01-17 10:11 ` Alex Bennée
2022-01-20 4:02 ` Viresh Kumar
2022-01-20 10:57 ` Michael S. Tsirkin
2022-01-20 15:41 ` Alex Bennée [this message]
2022-01-21 15:15 ` [RFC PATCH] tests/qtest: attempt to enable tests for virtio-gpio (!working) Alex Bennée
2022-03-31 9:52 ` Alex Bennée
2022-03-31 16:17 ` Stefan Hajnoczi
2022-04-04 17:59 ` Dr. David Alan Gilbert
2022-04-05 13:46 ` Alex Bennée
2022-01-20 11:25 ` [PATCH 0/2] virtio: Add vhost-user-gpio device's support Michael S. Tsirkin
2022-02-04 12:23 ` Michael S. Tsirkin
2022-02-04 13:52 ` Alex Bennée
2022-02-04 14:06 ` Michael S. Tsirkin
2022-03-31 9:58 ` Alex Bennée
2022-04-05 10:55 ` Alex Bennée
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=87ilue75zv.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stratos-dev@op-lists.linaro.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.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.