96a8326d69
Currently there is no way for user to set what features the driver should obey or not, it is hard wired in the code. In order to be able to debug the device behavior in case some feature is disabled, introduce a debugfs infrastructure with couple of files allowing user to see what features the device advertises and to set filter for features used by driver. Example: $cat /sys/bus/virtio/devices/virtio0/features 1110010111111111111101010000110010000000100000000000000000000000 $ echo "5" >/sys/kernel/debug/virtio/virtio0/filter_feature_add $ cat /sys/kernel/debug/virtio/virtio0/filter_features 5 $ echo "virtio0" > /sys/bus/virtio/drivers/virtio_net/unbind $ echo "virtio0" > /sys/bus/virtio/drivers/virtio_net/bind $ cat /sys/bus/virtio/devices/virtio0/features 1110000111111111111101010000110010000000100000000000000000000000 Note that sysfs "features" now already exists, this patch does not touch it. Signed-off-by: Jiri Pirko <jiri@nvidia.com> Acked-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Paolo Abeni <pabeni@redhat.com>
16 lines
809 B
Makefile
16 lines
809 B
Makefile
# SPDX-License-Identifier: GPL-2.0
|
|
obj-$(CONFIG_VIRTIO) += virtio.o virtio_ring.o
|
|
obj-$(CONFIG_VIRTIO_ANCHOR) += virtio_anchor.o
|
|
obj-$(CONFIG_VIRTIO_PCI_LIB) += virtio_pci_modern_dev.o
|
|
obj-$(CONFIG_VIRTIO_PCI_LIB_LEGACY) += virtio_pci_legacy_dev.o
|
|
obj-$(CONFIG_VIRTIO_MMIO) += virtio_mmio.o
|
|
obj-$(CONFIG_VIRTIO_PCI) += virtio_pci.o
|
|
virtio_pci-y := virtio_pci_modern.o virtio_pci_common.o
|
|
virtio_pci-$(CONFIG_VIRTIO_PCI_LEGACY) += virtio_pci_legacy.o
|
|
virtio_pci-$(CONFIG_VIRTIO_PCI_ADMIN_LEGACY) += virtio_pci_admin_legacy_io.o
|
|
obj-$(CONFIG_VIRTIO_BALLOON) += virtio_balloon.o
|
|
obj-$(CONFIG_VIRTIO_INPUT) += virtio_input.o
|
|
obj-$(CONFIG_VIRTIO_VDPA) += virtio_vdpa.o
|
|
obj-$(CONFIG_VIRTIO_MEM) += virtio_mem.o
|
|
obj-$(CONFIG_VIRTIO_DMA_SHARED_BUFFER) += virtio_dma_buf.o
|
|
obj-$(CONFIG_VIRTIO_DEBUG) += virtio_debug.o
|