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: Mon, 17 Jan 2022 10:11:21 +0000 [thread overview]
Message-ID: <871r16br9n.fsf@linaro.org> (raw)
In-Reply-To: <20220117034606-mutt-send-email-mst@kernel.org>
"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?
This is going to be a problem going forward as we have more out-of-tree
backends written as a first preference. While the first couple of vhost
devices have C implementations in contrib before we worked on the rust
version I think we are getting to the point of skipping a first C
version for future devices.
However I notice we have qtest/vhost-user-test.c so would that be enough
to ensure we can instantiate the device and a basic vhost-user
initialisation sequence doesn't cause it to crap out. This obviously
won't be exercising the virtq processing itself but does that really
exercise any of QEMU's boilerplate anyway?
> We also need some maintainers to step up.
You mean more reviewers for the vhost and virtio sections of QEMU's
maintainers?
>
>
>> --
>> Viresh
>>
>> Viresh Kumar (2):
>> hw/virtio: add boilerplate for vhost-user-gpio device
>> hw/virtio: add vhost-user-gpio-pci boilerplate
>>
>> hw/virtio/Kconfig | 5 +
>> hw/virtio/meson.build | 2 +
>> hw/virtio/vhost-user-gpio-pci.c | 69 ++++++
>> hw/virtio/vhost-user-gpio.c | 343 ++++++++++++++++++++++++++++
>> include/hw/virtio/vhost-user-gpio.h | 35 +++
>> 5 files changed, 454 insertions(+)
>> create mode 100644 hw/virtio/vhost-user-gpio-pci.c
>> create mode 100644 hw/virtio/vhost-user-gpio.c
>> create mode 100644 include/hw/virtio/vhost-user-gpio.h
>>
>> --
>> 2.31.1.272.g89b43f80a514
--
Alex Bennée
next prev parent reply other threads:[~2022-01-17 10:18 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 [this message]
2022-01-20 4:02 ` Viresh Kumar
2022-01-20 10:57 ` Michael S. Tsirkin
2022-01-20 15:41 ` Alex Bennée
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=871r16br9n.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 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).