Re: [Stratos-dev] Next VirtIO device for Project Stratos?

[Alex BennÃe <alex.bennee@linaro.org>]

Trilok Soni <quic_tsoni@quicinc.com> writes:

> On 6/1/2022 1:06 PM, Johannes Berg wrote:
>> Hi,
>> Not sure if there was anything you wanted me to comment on, but
>> since
>> I'm "the wifi guy" ... :)
>> 
>>>> mac80211 wlan / 10
>> FWIW, even though I'm the mac80211 maintainer, I'm not aware of a
>> specification or implementation of this ... I don't know what this is at
>> all.
>> 
>>>> mac80211 hwsim wireless simulation device / 29
>> This I implemented (both a driver in mac80211-hwsim in the kernel,
>> as
>> well as a device in wmediumd), but I wouldn't really necessarily
>> recommend using it for anything but testing.

I assume the use-case for this is something like a virtualised Android
OS. For cloud native testing I guess a simulation device provides enough of
what you need to exercise the guests network stack. However for real
deployments you need something to allow selection of networks and
reporting of network quality.

I'm not super familiar with the wifi stack but is this all usually
handled in one place or do multiple userspace daemons interrogate the
kernel APIs for this information?

If it all comes through one place perhaps it's enough for it to be given
a pipe to the host to make those queries - effectively creating a proxy
to the real host kernel interface?

>>> I am not sure if this related but virtio-ethernet keeps coming to us as
>>> requirement, I am not sure about the what is the support available in
>>> the various projects including Xen. This is a non-Mobile requirement
>>> particularly from the IOT or Auto segments. It will be nice to do adb
>>> over ethernet in the guest VM from the host shell.
>> For ethernet you have normal virtio-net.
>
> Thanks. Virtio-net is available, but I think e2e usecase w/ Type-1
> Hypervisor is what I am looking for. I believe CrosVM also supports
> Virtio-net but I am not sure if it works w/ Xen or not.

In normal Xen you would have a Dom0 with a traditional kernel driver to
service the backend. In a more modular setup you might want to have a
driver domain that combines the backend with the real HW driver running
as a unikernel?

>
> ---Trilok Soni


-- 
Alex BennÃe