Файловый менеджер - Редактировать - /var/www/xthruster/html/wp-content/uploads/flags/virtio.tar
Назад
virtio-trace/Makefile 0000644 00000000366 14722071152 0010622 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 CC = gcc CFLAGS = -O2 -Wall -pthread all: trace-agent .c.o: $(CC) $(CFLAGS) -c $^ -o $@ trace-agent: trace-agent.o trace-agent-ctl.o trace-agent-rw.o $(CC) $(CFLAGS) -o $@ $^ clean: rm -f *.o trace-agent ringtest/Makefile 0000644 00000001703 14722071152 0010045 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 all: all: ring virtio_ring_0_9 virtio_ring_poll virtio_ring_inorder ptr_ring noring CFLAGS += -Wall CFLAGS += -pthread -O2 -ggdb -flto -fwhole-program LDFLAGS += -pthread -O2 -ggdb -flto -fwhole-program main.o: main.c main.h ring.o: ring.c main.h ptr_ring.o: ptr_ring.c main.h ../../../include/linux/ptr_ring.h virtio_ring_0_9.o: virtio_ring_0_9.c main.h virtio_ring_poll.o: virtio_ring_poll.c virtio_ring_0_9.c main.h virtio_ring_inorder.o: virtio_ring_inorder.c virtio_ring_0_9.c main.h ring: ring.o main.o virtio_ring_0_9: virtio_ring_0_9.o main.o virtio_ring_poll: virtio_ring_poll.o main.o virtio_ring_inorder: virtio_ring_inorder.o main.o ptr_ring: ptr_ring.o main.o noring: noring.o main.o clean: -rm main.o -rm ring.o ring -rm virtio_ring_0_9.o virtio_ring_0_9 -rm virtio_ring_poll.o virtio_ring_poll -rm virtio_ring_inorder.o virtio_ring_inorder -rm ptr_ring.o ptr_ring -rm noring.o noring .PHONY: all clean ringtest/run-on-all.sh 0000755 00000001236 14722071152 0010731 0 ustar 00 #!/bin/sh # SPDX-License-Identifier: GPL-2.0 CPUS_ONLINE=$(lscpu --online -p=cpu|grep -v -e '#') #use last CPU for host. Why not the first? #many devices tend to use cpu0 by default so #it tends to be busier HOST_AFFINITY=$(echo "${CPUS_ONLINE}"|tail -n 1) #run command on all cpus for cpu in $CPUS_ONLINE do #Don't run guest and host on same CPU #It actually works ok if using signalling if (echo "$@" | grep -e "--sleep" > /dev/null) || \ test $HOST_AFFINITY '!=' $cpu then echo "GUEST AFFINITY $cpu" "$@" --host-affinity $HOST_AFFINITY --guest-affinity $cpu fi done echo "NO GUEST AFFINITY" "$@" --host-affinity $HOST_AFFINITY echo "NO AFFINITY" "$@" Makefile 0000644 00000000572 14722071152 0006211 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 obj-$(CONFIG_VIRTIO) += virtio.o virtio_ring.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 obj-$(CONFIG_VIRTIO_BALLOON) += virtio_balloon.o obj-$(CONFIG_VIRTIO_INPUT) += virtio_input.o vhost_test/Makefile 0000644 00000000136 14722071152 0010407 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only obj-m += vhost_test.o EXTRA_CFLAGS += -Idrivers/vhost Kconfig 0000644 00000005450 14722072576 0006067 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only config VIRTIO tristate ---help--- This option is selected by any driver which implements the virtio bus, such as CONFIG_VIRTIO_PCI, CONFIG_VIRTIO_MMIO, CONFIG_RPMSG or CONFIG_S390_GUEST. menuconfig VIRTIO_MENU bool "Virtio drivers" default y if VIRTIO_MENU config VIRTIO_PCI tristate "PCI driver for virtio devices" depends on PCI select VIRTIO ---help--- This driver provides support for virtio based paravirtual device drivers over PCI. This requires that your VMM has appropriate PCI virtio backends. Most QEMU based VMMs should support these devices (like KVM or Xen). If unsure, say M. config VIRTIO_PCI_LEGACY bool "Support for legacy virtio draft 0.9.X and older devices" default y depends on VIRTIO_PCI ---help--- Virtio PCI Card 0.9.X Draft (circa 2014) and older device support. This option enables building a transitional driver, supporting both devices conforming to Virtio 1 specification, and legacy devices. If disabled, you get a slightly smaller, non-transitional driver, with no legacy compatibility. So look out into your driveway. Do you have a flying car? If so, you can happily disable this option and virtio will not break. Otherwise, leave it set. Unless you're testing what life will be like in The Future. If unsure, say Y. config VIRTIO_PMEM tristate "Support for virtio pmem driver" depends on VIRTIO depends on LIBNVDIMM help This driver provides access to virtio-pmem devices, storage devices that are mapped into the physical address space - similar to NVDIMMs - with a virtio-based flushing interface. If unsure, say Y. config VIRTIO_BALLOON tristate "Virtio balloon driver" depends on VIRTIO select MEMORY_BALLOON ---help--- This driver supports increasing and decreasing the amount of memory within a KVM guest. If unsure, say M. config VIRTIO_INPUT tristate "Virtio input driver" depends on VIRTIO depends on INPUT ---help--- This driver supports virtio input devices such as keyboards, mice and tablets. If unsure, say M. config VIRTIO_MMIO tristate "Platform bus driver for memory mapped virtio devices" depends on HAS_IOMEM && HAS_DMA select VIRTIO ---help--- This drivers provides support for memory mapped virtio platform device driver. If unsure, say N. config VIRTIO_MMIO_CMDLINE_DEVICES bool "Memory mapped virtio devices parameter parsing" depends on VIRTIO_MMIO ---help--- Allow virtio-mmio devices instantiation via the kernel command line or module parameters. Be aware that using incorrect parameters (base address in particular) can crash your system - you have been warned. See Documentation/admin-guide/kernel-parameters.rst for details. If unsure, say 'N'. endif # VIRTIO_MENU
| ver. 1.4 |
Github
|
.
| PHP 7.4.3-4ubuntu2.24 | Генерация страницы: 0 |
proxy
|
phpinfo
|
Настройка