Changes in Kconfig

38968bcd - virtio-mem: s390 support

Fri, 25 Oct 2024 14:14:49 +0000

virtio-mem: s390 supportNow that s390 code is prepared for memory devices that reside above themaximum storage increment exposed through SCLP, everything is in placeto unlock virtio-mem support.As virtio-mem in Linux currently supports logically onlining/offliningmemory in pageblock granularity, we have an effective hot(un)pluggranularity of 1 MiB on s390.As virito-mem adds/removes individual Linux memory blocks (256MB), wewill currently never use gigantic pages in the identity mapping.It is worth noting that neither storage keys nor storage attributes (e.g.,data / nodat) are touched when onlining memory blocks, which is goodbecause we are not supposed to touch these parts for unplugged deviceblocks that are logically offline in Linux.We will currently never initialize storage keys for virtio-memmemory -- IOW, storage_key_init_range() is never called. It could be addedin the future when plugging device blocks. But as that functionessentially does nothing without modifying the code (changingPAGE_DEFAULT_ACC), that's just fine for now.kexec should work as intended and just like on other architectures thatsupport virtio-mem: we will never place kexec binaries on virtio-memmemory, and never indicate virtio-mem memory to the 2nd kernel. Thedevice driver in the 2nd kernel can simply reset the device --turning all memory unplugged, to then start plugging memory and addingthem to Linux, without causing trouble because the memory is alreadyused elsewhere.The special s390 kdump mode, whereby the 2nd kernel creates the ELFcore header, won't currently dump virtio-mem memory. The virtio-memdriver has a special kdump mode, from where we can detect memory rangesto dump. Based on this, support for dumping virtio-mem memory can beadded in the future fairly easily.Acked-by: Michael S. Tsirkin Tested-by: Mario Casquero Signed-off-by: David Hildenbrand Acked-by: Heiko Carstens Tested-by: Sumanth Korikkar Acked-by: Christian Borntraeger Link: https://lore.kernel.org/r/20241025141453.1210600-5-david@redhat.comSigned-off-by: Heiko Carstens List of files: /linux-6.15/drivers/virtio/Kconfig

0546d704 - virtio-mem: Enable virtio-mem for RISC-V

Wed, 05 Jun 2024 11:40:52 +0000

virtio-mem: Enable virtio-mem for RISC-VNow that RISC-V has memory hotplugging support, virtio-mem can be usedon the platform.Acked-by: David Hildenbrand Signed-off-by: Björn Töpel Link: https://lore.kernel.org/r/20240605114100.315918-10-bjorn@kernel.orgSigned-off-by: Palmer Dabbelt List of files: /linux-6.15/drivers/virtio/Kconfig

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/Kconfig

f51e146f - virtio-pci: Initialize the supported admin commands

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

virtio-pci: Initialize the supported admin commandsInitialize the supported admin commands upon activating the admin queue.The supported commands are saved as part of the admin queue context.Next patches in this series will expose APIs to use them.Reviewed-by: Feng Liu Acked-by: Michael S. Tsirkin Signed-off-by: Yishai Hadas Link: https://lore.kernel.org/r/20231219093247.170936-6-yishaih@nvidia.comSigned-off-by: Alex Williamson List of files: /linux-6.15/drivers/virtio/Kconfig

0b6fd46e - drivers/virtio: Clarify CONFIG_VIRTIO_MEM for unsupported architectures

Fri, 10 Jun 2022 09:47:37 +0000

drivers/virtio: Clarify CONFIG_VIRTIO_MEM for unsupported architecturesLet's make it clearer that simply unlocking CONFIG_VIRTIO_MEM on anarchitecture is most probably not sufficient to have it working asexpected.Cc: "Michael S. Tsirkin" Cc: Jason Wang Cc: Gavin Shan Signed-off-by: David Hildenbrand Message-Id: <20220610094737.65254-1-david@redhat.com>Signed-off-by: Michael S. Tsirkin List of files: /linux-6.15/drivers/virtio/Kconfig

ebe797f2 - virtio: VIRTIO_HARDEN_NOTIFICATION is broken

Thu, 30 Jun 2022 19:10:57 +0000

virtio: VIRTIO_HARDEN_NOTIFICATION is brokenThis option doesn't really work and breaks too many drivers.Not yet sure what's the right thing to do, for nowlet's make sure randconfig isn't broken by this.Fixes: c346dae4f3fb ("virtio: disable notification hardening by default")Cc: "Jason Wang" Signed-off-by: Michael S. Tsirkin Acked-by: Jason Wang List of files: /linux-6.15/drivers/virtio/Kconfig

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/Kconfig

c346dae4 - virtio: disable notification hardening by default

Wed, 22 Jun 2022 01:29:40 +0000

virtio: disable notification hardening by defaultWe try to harden virtio device notifications in 8b4ec69d7e09 ("virtio:harden vring IRQ"). It works with the assumption that the driver orcore can properly call virtio_device_ready() at the rightplace. Unfortunately, this seems to be not true and uncover variousbugs of the existing drivers, mainly the issue of usingvirtio_device_ready() incorrectly.So let's add a Kconfig option and disable it by default. It givesus time to fix the drivers and then we can consider re-enabling it.Signed-off-by: Jason Wang Message-Id: <20220622012940.21441-1-jasowang@redhat.com>Signed-off-by: Michael S. Tsirkin Reviewed-by: Cornelia Huck List of files: /linux-6.15/drivers/virtio/Kconfig

3f9dfbeb - virtio: replace arch_has_restricted_virtio_memory_access()

Mon, 06 Jun 2022 06:09:16 +0000

virtio: replace arch_has_restricted_virtio_memory_access()Instead of using arch_has_restricted_virtio_memory_access() togetherwith CONFIG_ARCH_HAS_RESTRICTED_VIRTIO_MEMORY_ACCESS, replace thosewith platform_has() and a new platform featurePLATFORM_VIRTIO_RESTRICTED_MEM_ACCESS.Signed-off-by: Juergen Gross Reviewed-by: Oleksandr Tyshchenko Tested-by: Oleksandr Tyshchenko # Arm64 onlyReviewed-by: Christoph Hellwig Acked-by: Borislav Petkov List of files: /linux-6.15/drivers/virtio/Kconfig

6f4abbaa - drivers/virtio: Enable virtio mem for ARM64

Wed, 19 Jan 2022 01:05:51 +0000

drivers/virtio: Enable virtio mem for ARM64This enables virtio-mem device support by allowing to enable thecorresponding kernel config option (CONFIG_VIRTIO_MEM) on thearchitecture.Signed-off-by: Gavin Shan Acked-by: David Hildenbrand Acked-by: Jonathan Cameron Acked-by: Michael S. Tsirkin Link: https://lore.kernel.org/r/20220119010551.181405-1-gshan@redhat.comSigned-off-by: Michael S. Tsirkin Signed-off-by: Gavin Shan Acked-by: David Hildenbrand Acked-by: Jonathan Cameron Acked-by: Michael S. Tsirkin List of files: /linux-6.15/drivers/virtio/Kconfig

e7c552ec - virtio: drop default for virtio-mem

Fri, 25 Feb 2022 11:46:34 +0000

virtio: drop default for virtio-memThere's no special reason why virtio-mem needs a default that'sdifferent from what kconfig provides, any more than e.g. virtio blk.Signed-off-by: Michael S. Tsirkin Acked-by: David Hildenbrand List of files: /linux-6.15/drivers/virtio/Kconfig

2128f4e2 - virtio-mem: disallow mapping virtio-mem memory via /dev/mem

Tue, 09 Nov 2021 02:35:53 +0000

virtio-mem: disallow mapping virtio-mem memory via /dev/memWe don't want user space to be able to map virtio-mem device memorydirectly (e.g., via /dev/mem) in order to have guarantees that in a sanesetup we'll never accidentially access unplugged memory within thedevice-managed region of a virtio-mem device, just as required by thevirtio-spec.As soon as the virtio-mem driver is loaded, the device region is visiblein /proc/iomem via the parent device region. From that point on userspace is aware of the device region and we want to disallow mappinganything inside that region (where we will dynamically (un)plug memory)until the driver has been unloaded cleanly and e.g., another driver mighttake over.By creating our parent IORESOURCE_SYSTEM_RAM resource withIORESOURCE_EXCLUSIVE, we will disallow any /dev/mem access to our deviceregion until the driver was unloaded cleanly and removed the parentregion. This will work even though only some memory blocks are actuallycurrently added to Linux and appear as busy in the resource tree.So access to the region from user space is only possiblea) if we don't load the virtio-mem driver.b) after unloading the virtio-mem driver cleanly.Don't build virtio-mem if access to /dev/mem cannot be restricticted -- ifwe have CONFIG_DEVMEM=y but CONFIG_STRICT_DEVMEM is not set.Link: https://lkml.kernel.org/r/20210920142856.17758-4-david@redhat.comSigned-off-by: David Hildenbrand Reviewed-by: Dan Williams Acked-by: Michael S. Tsirkin Cc: Andy Shevchenko Cc: Arnd Bergmann Cc: Greg Kroah-Hartman Cc: Hanjun Guo Cc: Jason Wang Cc: "Rafael J. Wysocki" Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/drivers/virtio/Kconfig

50f9481e - mm/memory_hotplug: remove CONFIG_MEMORY_HOTPLUG_SPARSE

Fri, 05 Nov 2021 20:44:24 +0000

mm/memory_hotplug: remove CONFIG_MEMORY_HOTPLUG_SPARSECONFIG_MEMORY_HOTPLUG depends on CONFIG_SPARSEMEM, so there is no need forCONFIG_MEMORY_HOTPLUG_SPARSE anymore; adjust all instances to useCONFIG_MEMORY_HOTPLUG and remove CONFIG_MEMORY_HOTPLUG_SPARSE.Link: https://lkml.kernel.org/r/20210929143600.49379-3-david@redhat.comSigned-off-by: David Hildenbrand Acked-by: Shuah Khan [kselftest]Acked-by: Greg Kroah-Hartman Acked-by: Oscar Salvador Cc: Alex Shi Cc: Andy Lutomirski Cc: Benjamin Herrenschmidt Cc: Borislav Petkov Cc: Dave Hansen Cc: "H. Peter Anvin" Cc: Ingo Molnar Cc: Jason Wang Cc: Jonathan Corbet Cc: Michael Ellerman Cc: "Michael S. Tsirkin" Cc: Michal Hocko Cc: Mike Rapoport Cc: Paul Mackerras Cc: Peter Zijlstra Cc: "Rafael J. Wysocki" Cc: Thomas Gleixner Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/drivers/virtio/Kconfig

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/Kconfig

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/Kconfig

0afa15e1 - virtio: let arch advertise guest's memory access restrictions

Thu, 10 Sep 2020 08:53:49 +0000

virtio: let arch advertise guest's memory access restrictionsAn architecture may restrict host access to guest memory,e.g. IBM s390 Secure Execution or AMD SEV.Provide a new Kconfig entry the architecture can select,CONFIG_ARCH_HAS_RESTRICTED_VIRTIO_MEMORY_ACCESS, when it providesthe arch_has_restricted_virtio_memory_access callback to advertiseto VIRTIO common code when the architecture restricts memory accessfrom the host.The common code can then fail the probe for any device whereVIRTIO_F_ACCESS_PLATFORM is required, but not set.Signed-off-by: Pierre Morel Reviewed-by: Cornelia Huck Reviewed-by: Halil Pasic Link: https://lore.kernel.org/r/1599728030-17085-2-git-send-email-pmorel@linux.ibm.comSigned-off-by: Michael S. Tsirkin Acked-by: Christian Borntraeger List of files: /linux-6.15/drivers/virtio/Kconfig

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/Kconfig

a96b0d06 - virtio-mem: Fix build error due to improper use 'select'

Fri, 19 Jun 2020 08:03:33 +0000

virtio-mem: Fix build error due to improper use 'select'As noted in:https://www.kernel.org/doc/Documentation/kbuild/kconfig-language.txt"select should be used with care. select will force a symbol to avalue without visiting the dependencies."Config VIRTIO_MEM should not select CONTIG_ALLOC directly.Otherwise it will cause an error:https://bugzilla.kernel.org/show_bug.cgi?id=208245Signed-off-by: Weilong Chen Link: https://lore.kernel.org/r/20200619080333.194753-1-chenweilong@huawei.comAcked-by: Randy Dunlap # build-testedSigned-off-by: Michael S. Tsirkin Acked-by: Jason Wang Acked-by: David Hildenbrand List of files: /linux-6.15/drivers/virtio/Kconfig

a7f7f624 - treewide: replace '---help---' in Kconfig files with 'help'

Sat, 13 Jun 2020 16:50:22 +0000

treewide: replace '---help---' in Kconfig files with 'help'Since commit 84af7a6194e4 ("checkpatch: kconfig: prefer 'help' over'---help---'"), the number of '---help---' has been graduallydecreasing, but there are still more than 2400 instances.This commit finishes the conversion. While I touched the lines,I also fixed the indentation.There are a variety of indentation styles found. a) 4 spaces + '---help---' b) 7 spaces + '---help---' c) 8 spaces + '---help---' d) 1 space + 1 tab + '---help---' e) 1 tab + '---help---' (correct indentation) f) 1 tab + 1 space + '---help---' g) 1 tab + 2 spaces + '---help---'In order to convert all of them to 1 tab + 'help', I ran thefollowing commend: $ find . -name 'Kconfig*' | xargs sed -i 's/^[[:space:]]*---help---/\thelp/'Signed-off-by: Masahiro Yamada List of files: /linux-6.15/drivers/virtio/Kconfig

255f5985 - virtio-mem: Paravirtualized memory hotunplug part 2

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

virtio-mem: Paravirtualized memory hotunplug part 2We also want to unplug online memory (contained in online memory blocksand, therefore, managed by the buddy), and eventually replug it later.When requested to unplug memory, we use alloc_contig_range() to allocatesubblocks in online memory blocks (so we are the owner) and send them toour hypervisor. When requested to plug memory, we can replug such memoryusing free_contig_range() after asking our hypervisor.We also want to mark all allocated pages PG_offline, so nobody willtouch them. To differentiate pages that were never onlined whenonlining the memory block from pages allocated via alloc_contig_range(), weuse PageDirty(). Based on this flag, virtio_mem_fake_online() can eitheronline the pages for the first time or use free_contig_range().It is worth noting that there are no guarantees on how much memory canactually get unplugged again. All device memory might completely befragmented with unmovable data, such that no subblock can get unplugged.We are not touching the ZONE_MOVABLE. If memory is onlined to theZONE_MOVABLE, it can only get unplugged after that memory was offlinedmanually by user space. In normal operation, virtio-mem memory issuggested to be onlined to ZONE_NORMAL. In the future, we will try tomake unplug more likely to succeed.Add a module parameter to control if online memory shall be touched.As we want to access alloc_contig_range()/free_contig_range() fromkernel module context, export the symbols.Note: Whenever virtio-mem uses alloc_contig_range(), all affected pagesare on the same node, in the same zone, and contain no holes.Acked-by: Michal Hocko # to export contig range allocator APITested-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: Mel Gorman Cc: Mike Rapoport Cc: Alexander Duyck Cc: Alexander Potapenko Signed-off-by: David Hildenbrand Link: https://lore.kernel.org/r/20200507140139.17083-6-david@redhat.comSigned-off-by: Michael S. Tsirkin List of files: /linux-6.15/drivers/virtio/Kconfig