qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Milan Zamazal <mzamazal@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org,  mst@redhat.com,  stefanha@redhat.com,
	 Vincent Guittot <vincent.guittot@linaro.org>
Subject: Re: [PATCH 0/4] Add SCMI vhost-user VIRTIO device
Date: Wed, 31 May 2023 13:57:41 +0200	[thread overview]
Message-ID: <87edmw7lxm.fsf@redhat.com> (raw)
In-Reply-To: <871qiwd9uq.fsf@linaro.org> ("Alex Bennée"'s message of "Wed, 31 May 2023 12:19:19 +0100")

Alex Bennée <alex.bennee@linaro.org> writes:

> Milan Zamazal <mzamazal@redhat.com> writes:
>
>> This patch series adds a vhost-user VIRTIO device for SCMI.
>> It's similar to other similar vhost-user VIRTIO devices.
>>
>> I'm aware of the work in progress by Alex Bennée to simplify similar devices
>> and avoid excessive code duplication.  I think the SCMI device support
>> doesn't bring anything special and it can be rebased on the given work
>> if/once it is merged.
>
> \o/ - I'll try and get the next iteration done in the next few weeks.

Great, looking forward.

> Out of interest have you tested your scmi backend with those patches? Oh
> and also which backend are you using?

I have tested the patches with my proof-of-concept SCMI backend
(emulating a fake sensor) based on rust-vmm and a Linux guest OS.  I
plan to change the prototype into something publishable in the next
weeks and to post patches to rust-vmm/vhost-device.

> Vincent did a bunch of work over the last year or so on SCMI although in
> his case the backend was a RTOS running in a separate domain using some
> shared memory between the SCMI domain and a couple of guests.

I have seen recordings of some related presentations.  The work is
primarily based on crosvm, right?  I'd be interested in what kind of
SCMI interface the domain provides and whether it would make sense to be
able to connect it with the QEMU SCMI device via some vhost-user daemon,
an already existing one, if any, and/or the one I work on.

>> Milan Zamazal (4):
>>   hw/virtio: Add boilerplate for vhost-user-scmi device
>>   hw/virtio: Add vhost-user-scmi-pci boilerplate
>>   tests/qtest: Fix a comment typo in vhost-user-test.c
>>   tests/qtest: enable tests for virtio-scmi
>>
>>  MAINTAINERS                         |   7 +
>>  hw/virtio/Kconfig                   |   5 +
>>  hw/virtio/meson.build               |   2 +
>>  hw/virtio/vhost-user-scmi-pci.c     |  68 +++++++
>>  hw/virtio/vhost-user-scmi.c         | 306 ++++++++++++++++++++++++++++
>>  include/hw/virtio/vhost-user-scmi.h |  30 +++
>>  tests/qtest/libqos/meson.build      |   1 +
>>  tests/qtest/libqos/virtio-scmi.c    | 174 ++++++++++++++++
>>  tests/qtest/libqos/virtio-scmi.h    |  34 ++++
>>  tests/qtest/vhost-user-test.c       |  46 ++++-
>>  10 files changed, 672 insertions(+), 1 deletion(-)
>>  create mode 100644 hw/virtio/vhost-user-scmi-pci.c
>>  create mode 100644 hw/virtio/vhost-user-scmi.c
>>  create mode 100644 include/hw/virtio/vhost-user-scmi.h
>>  create mode 100644 tests/qtest/libqos/virtio-scmi.c
>>  create mode 100644 tests/qtest/libqos/virtio-scmi.h



  reply	other threads:[~2023-05-31 11:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30 19:59 [PATCH 0/4] Add SCMI vhost-user VIRTIO device Milan Zamazal
2023-05-23  8:02 ` [PATCH 1/4] hw/virtio: Add boilerplate for vhost-user-scmi device Milan Zamazal
2023-05-23  8:19 ` [PATCH 2/4] hw/virtio: Add vhost-user-scmi-pci boilerplate Milan Zamazal
2023-05-23 14:38 ` [PATCH 4/4] tests/qtest: enable tests for virtio-scmi Milan Zamazal
2023-05-31  5:05   ` Thomas Huth
2023-05-24 13:34 ` [PATCH 3/4] tests/qtest: Fix a comment typo in vhost-user-test.c Milan Zamazal
2023-05-31  5:02   ` Thomas Huth
2023-05-31 11:06     ` Milan Zamazal
2023-05-31 11:19 ` [PATCH 0/4] Add SCMI vhost-user VIRTIO device Alex Bennée
2023-05-31 11:57   ` Milan Zamazal [this message]
2023-05-31 12:48     ` Vincent Guittot

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=87edmw7lxm.fsf@redhat.com \
    --to=mzamazal@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=vincent.guittot@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).