| Message ID | cover.1625806763.git.viresh.kumar@linaro.org |
|---|---|
| Headers | show |
| Series | virtio: Add vhost-user-i2c device's support | expand |
On Fri, Jul 09, 2021 at 10:30:15AM +0530, Viresh Kumar wrote: > Hello, > > This patchset adds vhost-user-i2c device's support in Qemu. Initially I tried to > add the backend implementation as well into Qemu, but as I was looking for a > hypervisor agnostic backend implementation, I decided to keep it outside of > Qemu. Eventually I implemented it in Rust and it works very well with this > patchset, and it is under review [1] to be merged in common rust vhost devices > crate. So I'm not sure whether it's appropriate to merge this right now. There are several spec change proposals before the virtio TC and I did not investigate whether this code reflects the spec before or after these changes. It seems prudent to wait until the spec changes are finalized and voted on, in any case. Pls ping me to merge once that has taken place. Thanks! > The kernel virtio I2C driver [2] is fully reviewed and is ready to be merged soon. > > V1->V2: > - Dropped the backend support from qemu and minor cleanups. > > I2C Testing: > ------------ > > I didn't have access to a real hardware where I can play with a I2C > client device (like RTC, eeprom, etc) to verify the working of the > backend daemon, so I decided to test it on my x86 box itself with > hierarchy of two ARM64 guests. > > The first ARM64 guest was passed "-device ds1338,address=0x20" option, > so it could emulate a ds1338 RTC device, which connects to an I2C bus. > Once the guest came up, ds1338 device instance was created within the > guest kernel by doing: > > echo ds1338 0x20 > /sys/bus/i2c/devices/i2c-0/new_device > > [ > Note that this may end up binding the ds1338 device to its driver, > which won't let our i2c daemon talk to the device. For that we need to > manually unbind the device from the driver: > > echo 0-0020 > /sys/bus/i2c/devices/0-0020/driver/unbind > ] > > After this is done, you will get /dev/rtc1. This is the device we wanted > to emulate, which will be accessed by the vhost-user-i2c backend daemon > via the /dev/i2c-0 file present in the guest VM. > > At this point we need to start the backend daemon and give it a > socket-path to talk to from qemu (you can pass -v to it to get more > detailed messages): > > vhost-user-i2c --socket-path=vi2c.sock -l 0:32 > > [ Here, 0:32 is the bus/device mapping, 0 for /dev/i2c-0 and 32 (i.e. > 0x20) is client address of ds1338 that we used while creating the > device. ] > > Now we need to start the second level ARM64 guest (from within the first > guest) to get the i2c-virtio.c Linux driver up. The second level guest > is passed the following options to connect to the same socket: > > -chardev socket,path=vi2c.sock0,id=vi2c \ > -device vhost-user-i2c-pci,chardev=vi2c,id=i2c > > Once the second level guest boots up, we will see the i2c-virtio bus at > /sys/bus/i2c/devices/i2c-X/. From there we can now make it emulate the > ds1338 device again by doing: > > > echo ds1338 0x20 > /sys/bus/i2c/devices/i2c-0/new_device > > [ This time we want ds1338's driver to be bound to the device, so it > should be enabled in the kernel as well. ] > > And we will get /dev/rtc1 device again here in the second level guest. > Now we can play with the rtc device with help of hwclock utility and we > can see the following sequence of transfers happening if we try to > update rtc's time from system time. > > hwclock -w -f /dev/rtc1 (in guest2) -> > Reaches i2c-virtio.c (Linux bus driver in guest2) -> > transfer over virtio -> > Reaches the qemu's vhost-i2c device emulation (running over guest1) -> > Reaches the backend daemon vhost-user-i2c started earlier (in guest1) -> > ioctl(/dev/i2c-0, I2C_RDWR, ..); (in guest1) -> > reaches qemu's hw/rtc/ds1338.c (running over host) > > > SMBUS Testing: > -------------- > > I wasn't required to have such a tedious setup for testing out with > SMBUS devices. I was able to emulate a SMBUS device on my x86 machine > using i2c-stub driver. > > $ modprobe i2c-stub chip_addr=0x20 > //Boot the arm64 guest now with i2c-virtio driver and then do: > $ echo al3320a 0x20 > /sys/class/i2c-adapter/i2c-0/new_device > $ cat /sys/bus/iio/devices/iio:device0/in_illuminance_raw > > That's it. > > I hope I was able to give a clear picture of my test setup here :) > > -- > Viresh > > Viresh Kumar (3): > hw/virtio: add boilerplate for vhost-user-i2c device > hw/virtio: add vhost-user-i2c-pci boilerplate > MAINTAINERS: Add entry for virtio-i2c > > MAINTAINERS | 7 + > hw/virtio/Kconfig | 5 + > hw/virtio/meson.build | 2 + > hw/virtio/vhost-user-i2c-pci.c | 69 +++++++ > hw/virtio/vhost-user-i2c.c | 288 +++++++++++++++++++++++++++++ > include/hw/virtio/vhost-user-i2c.h | 28 +++ > 6 files changed, 399 insertions(+) > create mode 100644 hw/virtio/vhost-user-i2c-pci.c > create mode 100644 hw/virtio/vhost-user-i2c.c > create mode 100644 include/hw/virtio/vhost-user-i2c.h > > -- > 2.31.1.272.g89b43f80a514
On 04-09-21, 15:44, Michael S. Tsirkin wrote: > So I'm not sure whether it's appropriate to merge this right now. This is already merged. > There are several spec change proposals before the virtio TC > and I did not investigate whether this code reflects the > spec before or after these changes. I believe you are talking about the zero-length stuff, right ? This patchset doesn't depend on that and won't change with or without those patches. The backend is implemented separately in Rust. https://github.com/rust-vmm/vhost-device > It seems prudent to wait > until the spec changes are finalized and voted on, in any case. I will update both the Linux driver and Rust implementation once we accept the changes for spec. -- viresh
Hello, This patchset adds vhost-user-i2c device's support in Qemu. Initially I tried to add the backend implementation as well into Qemu, but as I was looking for a hypervisor agnostic backend implementation, I decided to keep it outside of Qemu. Eventually I implemented it in Rust and it works very well with this patchset, and it is under review [1] to be merged in common rust vhost devices crate. The kernel virtio I2C driver [2] is fully reviewed and is ready to be merged soon. V1->V2: - Dropped the backend support from qemu and minor cleanups. I2C Testing: ------------ I didn't have access to a real hardware where I can play with a I2C client device (like RTC, eeprom, etc) to verify the working of the backend daemon, so I decided to test it on my x86 box itself with hierarchy of two ARM64 guests. The first ARM64 guest was passed "-device ds1338,address=0x20" option, so it could emulate a ds1338 RTC device, which connects to an I2C bus. Once the guest came up, ds1338 device instance was created within the guest kernel by doing: echo ds1338 0x20 > /sys/bus/i2c/devices/i2c-0/new_device [ Note that this may end up binding the ds1338 device to its driver, which won't let our i2c daemon talk to the device. For that we need to manually unbind the device from the driver: echo 0-0020 > /sys/bus/i2c/devices/0-0020/driver/unbind ] After this is done, you will get /dev/rtc1. This is the device we wanted to emulate, which will be accessed by the vhost-user-i2c backend daemon via the /dev/i2c-0 file present in the guest VM. At this point we need to start the backend daemon and give it a socket-path to talk to from qemu (you can pass -v to it to get more detailed messages): vhost-user-i2c --socket-path=vi2c.sock -l 0:32 [ Here, 0:32 is the bus/device mapping, 0 for /dev/i2c-0 and 32 (i.e. 0x20) is client address of ds1338 that we used while creating the device. ] Now we need to start the second level ARM64 guest (from within the first guest) to get the i2c-virtio.c Linux driver up. The second level guest is passed the following options to connect to the same socket: -chardev socket,path=vi2c.sock0,id=vi2c \ -device vhost-user-i2c-pci,chardev=vi2c,id=i2c Once the second level guest boots up, we will see the i2c-virtio bus at /sys/bus/i2c/devices/i2c-X/. From there we can now make it emulate the ds1338 device again by doing: echo ds1338 0x20 > /sys/bus/i2c/devices/i2c-0/new_device [ This time we want ds1338's driver to be bound to the device, so it should be enabled in the kernel as well. ] And we will get /dev/rtc1 device again here in the second level guest. Now we can play with the rtc device with help of hwclock utility and we can see the following sequence of transfers happening if we try to update rtc's time from system time. hwclock -w -f /dev/rtc1 (in guest2) -> Reaches i2c-virtio.c (Linux bus driver in guest2) -> transfer over virtio -> Reaches the qemu's vhost-i2c device emulation (running over guest1) -> Reaches the backend daemon vhost-user-i2c started earlier (in guest1) -> ioctl(/dev/i2c-0, I2C_RDWR, ..); (in guest1) -> reaches qemu's hw/rtc/ds1338.c (running over host) SMBUS Testing: -------------- I wasn't required to have such a tedious setup for testing out with SMBUS devices. I was able to emulate a SMBUS device on my x86 machine using i2c-stub driver. $ modprobe i2c-stub chip_addr=0x20 //Boot the arm64 guest now with i2c-virtio driver and then do: $ echo al3320a 0x20 > /sys/class/i2c-adapter/i2c-0/new_device $ cat /sys/bus/iio/devices/iio:device0/in_illuminance_raw That's it. I hope I was able to give a clear picture of my test setup here :) -- Viresh Viresh Kumar (3): hw/virtio: add boilerplate for vhost-user-i2c device hw/virtio: add vhost-user-i2c-pci boilerplate MAINTAINERS: Add entry for virtio-i2c MAINTAINERS | 7 + hw/virtio/Kconfig | 5 + hw/virtio/meson.build | 2 + hw/virtio/vhost-user-i2c-pci.c | 69 +++++++ hw/virtio/vhost-user-i2c.c | 288 +++++++++++++++++++++++++++++ include/hw/virtio/vhost-user-i2c.h | 28 +++ 6 files changed, 399 insertions(+) create mode 100644 hw/virtio/vhost-user-i2c-pci.c create mode 100644 hw/virtio/vhost-user-i2c.c create mode 100644 include/hw/virtio/vhost-user-i2c.h -- 2.31.1.272.g89b43f80a514