Hi Viresh, Linus, On Fri, Jun 11, 2021 at 5:56 AM Viresh Kumar <viresh.kumar@xxxxxxxxxx> wrote: > On 10-06-21, 22:46, Linus Walleij wrote: > > thanks for working on this, it's a really interesting driver. > > > > My first question is conceptual: > > > > We previously have Geerts driver for virtualization: > > drivers/gpio/gpio-aggregator.c > > > > The idea with the aggregator is that a host script sets up a > > unique gpiochip for the virtualized instance using some poking > > in sysfs and pass that to the virtual machine. > > So this is Linux acting as virtualization host by definition. The gpio-aggregator is running on the host... > > I think virtio is more abstract and intended for the usecase > > where the hypervisor is not Linux, so this should be mentioned > > in the commit, possibly also in Kconfig so users immediately > > know what usecases the two different drivers are for. ... while the virtio-gpio driver is meant for the guest kernel. I my PoC "[PATCH QEMU v2 0/5] Add a GPIO backend"[1], I didn't have a virtio transport, but just hooked into the PL061 GPIO emulation in QEMU. The PL061 QEMU driver talked to the GPIO backend, which talked to /dev/gpiochipN on the host. > Well, not actually. > > The host can actually be anything. It can be a Xen based dom0, which > runs some proprietary firmware, or Qemu running over Linux. > > It is left for the host to decide how it wants to club together the > GPIO pins from host and access them, with Linux host userspace it > would be playing with /dev/gpiochipN, while for a raw one it may > be accessing registers directly. > > And so the backend running at host, needs to pass the gpiochip > configurations and only the host understand it. So QEMU has to translate the virtio-gpio communication to e.g. /dev/gpiochipN on the host (or a different backend on non-Linux or bare-metal HV). > The way I test it for now is by running this with Qemu over my x86 > box, so my host side is indeed playing with sysfs Linux. Can you please share a link to the QEMU patches? > > Possibly both could be used: aggregator to pick out the GPIOs > > you want into a synthetic GPIO chip, and the actual talk > > between the hypervisor/host and the guest using virtio, even > > with linux-on-linux. > > Not sure if I understand the aggregator thing for now, but we see the > backend running at host (which talks to this Linux driver at guest) as > a userspace thing and not a kernel driver. Not sure if aggregator can > be used like that, but anyway.. The GPIO aggregator came into play after talking to Alexander Graf and Peter Maydell. To reduce the attack surface, they didn't want QEMU to be responsible for exporting to the guest a subset of all GPIOs of a gpiochip, only a full gpiochip. However, the full gpiochip may contain critical GPIOs you do not want the guest to tamper with. Hence the GPIO aggregator was born, to take care of aggregating all GPIOs you want to export to a guest into a new virtual gpiochip. You can find more information about the GPIO Aggregator's use cases in "[PATCH v7 0/6] gpio: Add GPIO Aggregator"[2]. [1] https://lore.kernel.org/linux-gpio/20200423090118.11199-1-geert+renesas@xxxxxxxxx [2] https://lore.kernel.org/linux-doc/20200511145257.22970-1-geert+renesas@xxxxxxxxx/ Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
