Changes in Makefile

96a8326d - virtio: add debugfs infrastructure to allow to debug virtio features

Wed, 24 Apr 2024 10:40:45 +0000

virtio: add debugfs infrastructure to allow to debug virtio featuresCurrently there is no way for user to set what features the drivershould obey or not, it is hard wired in the code.In order to be able to debug the device behavior in case some feature isdisabled, introduce a debugfs infrastructure with couple of filesallowing user to see what features the device advertises andto set filter for features used by driver.Example:$cat /sys/bus/virtio/devices/virtio0/features1110010111111111111101010000110010000000100000000000000000000000$ echo "5" >/sys/kernel/debug/virtio/virtio0/filter_feature_add$ cat /sys/kernel/debug/virtio/virtio0/filter_features5$ echo "virtio0" > /sys/bus/virtio/drivers/virtio_net/unbind$ echo "virtio0" > /sys/bus/virtio/drivers/virtio_net/bind$ cat /sys/bus/virtio/devices/virtio0/features1110000111111111111101010000110010000000100000000000000000000000Note that sysfs "features" now already exists, this patch does nottouch it.Signed-off-by: Jiri Pirko Acked-by: Michael S. Tsirkin Signed-off-by: Paolo Abeni List of files: /linux-6.15/drivers/virtio/Makefile

c3fc3e09 - virtio-pci: Introduce APIs to execute legacy IO admin commands

Tue, 19 Dec 2023 09:32:44 +0000

virtio-pci: Introduce APIs to execute legacy IO admin commandsIntroduce APIs to execute legacy IO admin commands.It includes: io_legacy_read/write for both common and the deviceconfiguration, io_legacy_notify_info.In addition, exposing an API to check whether the legacy IO commands aresupported. (i.e. virtio_pci_admin_has_legacy_io()).Those APIs will be used by the next patches from this series.Note:Unlike modern drivers which support hardware virtio devices, legacydrivers assume software-based devices: e.g. they don't use proper memorybarriers on ARM, use big endian on PPC, etc. X86 drivers are mostly okthough, more or less by chance. For now, only support legacy IO on X86.Acked-by: Michael S. Tsirkin Signed-off-by: Yishai Hadas Link: https://lore.kernel.org/r/20231219093247.170936-7-yishaih@nvidia.comSigned-off-by: Alex Williamson List of files: /linux-6.15/drivers/virtio/Makefile

a603002e - virtio: replace restricted mem access flag with callback

Wed, 22 Jun 2022 06:38:36 +0000

virtio: replace restricted mem access flag with callbackInstead of having a global flag to require restricted memory accessfor all virtio devices, introduce a callback which can select thatrequirement on a per-device basis.For convenience add a common function returning always true, which canbe used for use cases like SEV.Per default use a callback always returning false.As the callback needs to be set in early init code already, add avirtio anchor which is builtin in case virtio is enabled.Signed-off-by: Juergen Gross Tested-by: Oleksandr Tyshchenko # Arm64 guest using XenReviewed-by: Stefano Stabellini Link: https://lore.kernel.org/r/20220622063838.8854-2-jgross@suse.comSigned-off-by: Juergen Gross List of files: /linux-6.15/drivers/virtio/Makefile

d89c8169 - virtio-pci: introduce legacy device module

Fri, 29 Oct 2021 09:14:42 +0000

virtio-pci: introduce legacy device moduleSplit common codes from virtio-pci-legacy so vDPA driver can reuse itlater.Signed-off-by: Wu Zongyong Acked-by: Jason Wang Link: https://lore.kernel.org/r/71605acde5e97fcb2760a6973e406279fb1bbd33.1635493219.git.wuzongyong@linux.alibaba.comSigned-off-by: Michael S. Tsirkin List of files: /linux-6.15/drivers/virtio/Makefile

fd502729 - virtio-pci: introduce modern device module

Mon, 04 Jan 2021 06:55:00 +0000

virtio-pci: introduce modern device moduleSigned-off-by: Jason Wang Link: https://lore.kernel.org/r/20210104065503.199631-17-jasowang@redhat.comIncluding a bugfix:virtio: don't prompt CONFIG_VIRTIO_PCI_MODERNCc: Arnd Bergmann Cc: Anders Roxell Cc: Guenter Roeck Reported-by: Naresh Kamboju Fixes: 86b87c9d858b6 ("virtio-pci: introduce modern device module")Signed-off-by: Jason Wang Acked-by: Arnd Bergmann Link: https://lore.kernel.org/r/20210223061905.422659-2-jasowang@redhat.comSigned-off-by: Michael S. Tsirkin List of files: /linux-6.15/drivers/virtio/Makefile

9fe2f897 - virtio: fix build for configs without dma-bufs

Wed, 19 Aug 2020 03:10:11 +0000

virtio: fix build for configs without dma-bufsReported-by: kernel test robot Signed-off-by: David Stevens Link: http://patchwork.freedesktop.org/patch/msgid/20200819031011.310180-1-stevensd@chromium.orgSigned-off-by: Gerd Hoffmann List of files: /linux-6.15/drivers/virtio/Makefile

a0308938 - virtio: add dma-buf support for exported objects

Tue, 18 Aug 2020 07:13:41 +0000

virtio: add dma-buf support for exported objectsThis change adds a new flavor of dma-bufs that can be used by virtiodrivers to share exported objects. A virtio dma-buf can be queried byvirtio drivers to obtain the UUID which identifies the underlyingexported object.Signed-off-by: David Stevens Acked-by: Michael S. Tsirkin Link: http://patchwork.freedesktop.org/patch/msgid/20200818071343.3461203-2-stevensd@chromium.orgSigned-off-by: Gerd Hoffmann List of files: /linux-6.15/drivers/virtio/Makefile

5f1f79bb - virtio-mem: Paravirtualized memory hotplug

Thu, 07 May 2020 14:01:25 +0000

virtio-mem: Paravirtualized memory hotplugEach virtio-mem device owns exactly one memory region. It is responsiblefor adding/removing memory from that memory region on request.When the device driver starts up, the requested amount of memory isqueried and then plugged to Linux. On request, further memory can beplugged or unplugged. This patch only implements the plugging part.On x86-64, memory can currently be plugged in 4MB ("subblock") granularity.When required, a new memory block will be added (e.g., usually 128MB onx86-64) in order to plug more subblocks. Only x86-64 was tested for now.The online_page callback is used to keep unplugged subblocks offlinewhen onlining memory - similar to the Hyper-V balloon driver. Unpluggedpages are marked PG_offline, to tell dump tools (e.g., makedumpfile) toskip them.User space is usually responsible for onlining the added memory. Thememory hotplug notifier is used to synchronize virtio-mem activityagainst memory onlining/offlining.Each virtio-mem device can belong to a NUMA node, which allows us toeasily add/remove small chunks of memory to/from a specific NUMA node byusing multiple virtio-mem devices. Something that works even when theguest has no idea about the NUMA topology.One way to view virtio-mem is as a "resizable DIMM" or a DIMM with many"sub-DIMMS".This patch directly introduces the basic infrastructure to implement memoryunplug. Especially the memory block states and subblock bitmaps will beheavily used there.Notes:- In case memory is to be onlined by user space, we limit the amount of offline memory blocks, to not run out of memory. This is esp. an issue if memory is added faster than it is getting onlined.- Suspend/Hibernate is not supported due to the way virtio-mem devices behave. Limited support might be possible in the future.- Reloading the device driver is not supported.Reviewed-by: Pankaj Gupta Tested-by: Pankaj Gupta Cc: "Michael S. Tsirkin" Cc: Jason Wang Cc: Oscar Salvador Cc: Michal Hocko Cc: Igor Mammedov Cc: Dave Young Cc: Andrew Morton Cc: Dan Williams Cc: Pavel Tatashin Cc: Stefan Hajnoczi Cc: Vlastimil Babka Cc: "Rafael J. Wysocki" Cc: Len Brown Cc: linux-acpi@vger.kernel.orgSigned-off-by: David Hildenbrand Link: https://lore.kernel.org/r/20200507140139.17083-2-david@redhat.comSigned-off-by: Michael S. Tsirkin List of files: /linux-6.15/drivers/virtio/Makefile

c9b9f5f8 - vdpa: move to drivers/vdpa

Tue, 31 Mar 2020 19:15:14 +0000

vdpa: move to drivers/vdpaWe have both vhost and virtio drivers that depend on vdpa.It's easier to locate it at a top level directory otherwisewe run into issues e.g. if vhost is built-in but virtiois modular. Let's just move it up a level.Reported-by: Randy Dunlap Signed-off-by: Michael S. Tsirkin List of files: /linux-6.15/drivers/virtio/Makefile

c043b4a8 - virtio: introduce a vDPA based transport

Thu, 26 Mar 2020 14:01:22 +0000

virtio: introduce a vDPA based transportThis patch introduces a vDPA transport for virtio. This is used touse kernel virtio driver to drive the vDPA device that is capableof populating virtqueue directly.A new virtio-vdpa driver will be registered to the vDPA bus, when anew virtio-vdpa device is probed, it will register the device withvdpa based config ops. This means it is a software transport betweenvDPA driver and vDPA device. The transport was implemented throughbus_ops of vDPA parent.Signed-off-by: Jason Wang Link: https://lore.kernel.org/r/20200326140125.19794-7-jasowang@redhat.comSigned-off-by: Michael S. Tsirkin List of files: /linux-6.15/drivers/virtio/Makefile

961e9c84 - vDPA: introduce vDPA bus

Thu, 26 Mar 2020 14:01:21 +0000

vDPA: introduce vDPA busvDPA device is a device that uses a datapath which complies with thevirtio specifications with vendor specific control path. vDPA devicescan be both physically located on the hardware or emulated bysoftware. vDPA hardware devices are usually implemented through PCIEwith the following types:- PF (Physical Function) - A single Physical Function- VF (Virtual Function) - Device that supports single root I/O virtualization (SR-IOV). Its Virtual Function (VF) represents a virtualized instance of the device that can be assigned to different partitions- ADI (Assignable Device Interface) and its equivalents - With technologies such as Intel Scalable IOV, a virtual device (VDEV) composed by host OS utilizing one or more ADIs. Or its equivalent like SF (Sub function) from Mellanox.>From a driver's perspective, depends on how and where the DMAtranslation is done, vDPA devices are split into two types:- Platform specific DMA translation - From the driver's perspective, the device can be used on a platform where device access to data in memory is limited and/or translated. An example is a PCIE vDPA whose DMA request was tagged via a bus (e.g PCIE) specific way. DMA translation and protection are done at PCIE bus IOMMU level.- Device specific DMA translation - The device implements DMA isolation and protection through its own logic. An example is a vDPA device which uses on-chip IOMMU.To hide the differences and complexity of the above types for a vDPAdevice/IOMMU options and in order to present a generic virtio deviceto the upper layer, a device agnostic framework is required.This patch introduces a software vDPA bus which abstracts thecommon attributes of vDPA device, vDPA bus driver and thecommunication method (vdpa_config_ops) between the vDPA deviceabstraction and the vDPA bus driver. This allows multiple types ofdrivers to be used for vDPA device like the virtio_vdpa and vhost_vdpadriver to operate on the bus and allow vDPA device could be used byeither kernel virtio driver or userspace vhost drivers as: virtio drivers vhost drivers | | [virtio bus] [vhost uAPI] | | virtio device vhost device virtio_vdpa drv vhost_vdpa drv \ / [vDPA bus] | vDPA device hardware drv | [hardware bus] | vDPA hardwareWith the abstraction of vDPA bus and vDPA bus operations, thedifference and complexity of the under layer hardware is hidden fromupper layer. The vDPA bus drivers on top can use a unifiedvdpa_config_ops to control different types of vDPA device.Signed-off-by: Jason Wang Link: https://lore.kernel.org/r/20200326140125.19794-6-jasowang@redhat.comSigned-off-by: Michael S. Tsirkin List of files: /linux-6.15/drivers/virtio/Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/virtio/Makefile

271c8651 - Add virtio-input driver.

Fri, 27 Mar 2015 02:16:12 +0000

Add virtio-input driver.virtio-input is basically evdev-events-over-virtio, so this driver isn'tmuch more than reading configuration from config space and forwardingincoming events to the linux input layer.Signed-off-by: Gerd Hoffmann Acked-by: Michael S. Tsirkin Signed-off-by: Rusty Russell List of files: /linux-6.15/drivers/virtio/Makefile

46506da5 - virtio_pci: add an option to disable legacy driver

Thu, 15 Jan 2015 14:06:26 +0000

virtio_pci: add an option to disable legacy driverUseful for testing device virtio 1 compatibility.Based on patch by Rusty - couldn't resist puttingthat flying car joke in there!Signed-off-by: Michael S. Tsirkin Signed-off-by: Rusty Russell List of files: /linux-6.15/drivers/virtio/Makefile

1fcf0512 - virtio_pci: modern driver

Thu, 11 Dec 2014 11:59:51 +0000

virtio_pci: modern driverLightly tested against qemu.One thing *not* implemented here is separate mappingsfor descriptor/avail/used rings. That's nice to have,will be done later after we have core support.This also exposes the PCI layout to userspace, andadds macros for PCI layout offsets:QEMU wants it, so why not? Trust, but verify.Signed-off-by: Rusty Russell Signed-off-by: Michael S. Tsirkin List of files: /linux-6.15/drivers/virtio/Makefile

5f4c9760 - virtio_pci: rename virtio_pci -> virtio_pci_common

Mon, 08 Dec 2014 14:39:45 +0000

virtio_pci: rename virtio_pci -> virtio_pci_commonkbuild does not seem to like it when we name sourcefiles same as the module.Let's rename virtio_pci -> virtio_pci_common,and get rid of #include-ing c files.Signed-off-by: Michael S. Tsirkin List of files: /linux-6.15/drivers/virtio/Makefile

eccbb05a - virtio: remove CONFIG_VIRTIO_RING

Fri, 28 Sep 2012 05:35:15 +0000

virtio: remove CONFIG_VIRTIO_RINGEveryone who selects VIRTIO is also made to select VIRTIO_RING; just makethem synonymous, since we removed the indirection layer some time ago.Signed-off-by: Rusty Russell List of files: /linux-6.15/drivers/virtio/Makefile

edfd52e6 - virtio: Add platform bus driver for memory mapped virtio device

Mon, 24 Oct 2011 13:07:03 +0000

virtio: Add platform bus driver for memory mapped virtio deviceThis patch, based on virtio PCI driver, adds support for memorymapped (platform) virtio device. This should allow environmentslike qemu to use virtio-based block & network devices even onplatforms without PCI support.One can define and register a platform device which resourceswill describe memory mapped control registers and "mailbox"interrupt. Such device can be also instantiated using the DeviceTree node with compatible property equal "virtio,mmio".Cc: Anthony Liguori Cc: Michael S.Tsirkin Signed-off-by: Pawel Moll Signed-off-by: Rusty Russell List of files: /linux-6.15/drivers/virtio/Makefile

6b35e407 - virtio: balloon driver

Tue, 05 Feb 2008 04:50:12 +0000

virtio: balloon driverAfter discussions with Anthony Liguori, it seems that the virtioballoon can be made even simpler. Here's my attempt.The device configuration tells the driver how much memory it shouldtake from the guest (ie. balloon size). The guest feeds the pagenumbers it has taken via one virtqueue.A second virtqueue feeds the page numbers the driver wants back: ifthe device has the VIRTIO_BALLOON_F_MUST_TELL_HOST bit, then thisqueue is compulsory, otherwise it's advisory (and the guest can simplyfault the pages back in).This driver can be enhanced later to deflate the balloon via ashrinker, oom callback or we could even go for a complete set ofin-guest regulators.Signed-off-by: Rusty Russell List of files: /linux-6.15/drivers/virtio/Makefile

3343660d - virtio: PCI device

Tue, 13 Nov 2007 03:30:26 +0000

virtio: PCI deviceThis is a PCI device that implements a transport for virtio. It allows virtiodevices to be used by QEMU based VMMs like KVM or Xen.Signed-off-by: Anthony Liguori Signed-off-by: Rusty Russell List of files: /linux-6.15/drivers/virtio/Makefile