[U-Boot] [PATCH 00/27] virtio: Introduce VirtIO driver support
Simon Glass
sjg at chromium.org
Thu Sep 27 13:43:10 UTC 2018
Hi Bin,
On 23 September 2018 at 06:41, Bin Meng <bmeng.cn at gmail.com> wrote:
> This series brings in VirtIO driver support in U-Boot. The work is based
> on Tuomas's virtio support on QEMU ARM targets.
>
> VirtIO is a virtualization standard for network and disk device drivers
> where just the guest's device driver "knows" it is running in a virtual
> environment, and cooperates with the hypervisor. This enables guests to
> get high performance network and disk operations, and gives most of the
> performance benefits of paravirtualization. In the U-Boot case, the
> guest is U-Boot itself, while the virtual environment are normally QEMU
> targets like ARM, RISC-V and x86.
>
> Both VirtIO MMIO and PCI transport options are supported. Only VirtIO
> network and block device drivers are supported for now.
>
> The following QEMU targets are supported.
>
> - qemu_arm_defconfig
> - qemu_arm64_defconfig
> - qemu-riscv32_defconfig
> - qemu-riscv64_defconfig
> - qemu-x86_defconfig
> - qemu-x86_64_defconfig
>
> A new child_post_probe() uclass driver method is introduced to better
> support virtio device driver. This also changes BLK uclass driver to
> supply a post_probe() method which calls part_init(), so that we can
> avoid duplicating such call in every BLK driver.
>
> Not every checkpatch warning reported was fixed, but I tried to fix as
> many as possible which makes sense.
>
> This series needs to be applied after the risc-v QEMU series is applied.
>
> This series is available at u-boot-x86/virtio-working for testing.
> Note the branch already contains the risc-v QEMU series plus one network
> stack fix to make virtio-net driver happy.
>
Looks like a very nice implementation.
How does this all get tested? Could we have a simple sandbox driver?
Regards,
Simon
More information about the U-Boot
mailing list