Changes in Kconfig

0f2946bb - xen: Change xen-acpi-processor dom0 dependency

Mon, 31 Mar 2025 17:29:12 +0000

xen: Change xen-acpi-processor dom0 dependencyxen-acpi-processor functions under a PVH dom0 with only axen_initial_domain() runtime check. Change the Kconfig dependency fromPV dom0 to generic dom0 to reflect that.Suggested-by: Jan Beulich Signed-off-by: Jason Andryuk Reviewed-by: Juergen Gross Tested-by: Jan Beulich Signed-off-by: Juergen Gross Message-ID: <20250331172913.51240-1-jason.andryuk@amd.com> List of files: /linux-6.15/drivers/xen/Kconfig

0fd2a743 - xen: Remove dependency between pciback and privcmd

Sat, 12 Oct 2024 08:45:37 +0000

xen: Remove dependency between pciback and privcmdCommit 2fae6bb7be32 ("xen/privcmd: Add new syscall to get gsi from dev")adds a weak reverse dependency to the config XEN_PRIVCMD definition, thatdependency causes xen-privcmd can't be loaded on domU, because dependentxen-pciback isn't always be loaded successfully on domU.To solve above problem, remove that dependency, and do not callpcistub_get_gsi_from_sbdf() directly, instead add a hook indrivers/xen/apci.c, xen-pciback register the real call function, then inprivcmd_ioctl_pcidev_get_gsi call that hook.Fixes: 2fae6bb7be32 ("xen/privcmd: Add new syscall to get gsi from dev")Reported-by: Marek Marczykowski-Górecki Signed-off-by: Jiqian Chen Reviewed-by: Juergen Gross Message-ID: <20241012084537.1543059-1-Jiqian.Chen@amd.com>Signed-off-by: Juergen Gross List of files: /linux-6.15/drivers/xen/Kconfig

9af48210 - xen: Fix config option reference in XEN_PRIVCMD definition

Mon, 30 Sep 2024 09:06:50 +0000

xen: Fix config option reference in XEN_PRIVCMD definitionCommit 2fae6bb7be32 ("xen/privcmd: Add new syscall to get gsi from dev")adds a weak reverse dependency to the config XEN_PRIVCMD definition,referring to CONFIG_XEN_PCIDEV_BACKEND. In Kconfig files, one refers toconfig options without the CONFIG prefix, though. So in its current form,this does not create the reverse dependency as intended, but is anattribute with no effect.Refer to the intended config option XEN_PCIDEV_BACKEND in the XEN_PRIVCMDdefinition.Fixes: 2fae6bb7be32 ("xen/privcmd: Add new syscall to get gsi from dev")Signed-off-by: Lukas Bulwahn Reviewed-by: Juergen Gross Message-ID: <20240930090650.429813-1-lukas.bulwahn@redhat.com>Signed-off-by: Juergen Gross List of files: /linux-6.15/drivers/xen/Kconfig

2fae6bb7 - xen/privcmd: Add new syscall to get gsi from dev

Tue, 24 Sep 2024 06:14:37 +0000

xen/privcmd: Add new syscall to get gsi from devOn PVH dom0, when passthrough a device to domU, QEMU and xl toolswant to use gsi number to do pirq mapping, see QEMU codexen_pt_realize->xc_physdev_map_pirq, and xl codepci_add_dm_done->xc_physdev_map_pirq, but in current codes, the gsinumber is got from file /sys/bus/pci/devices//irq, that iswrong, because irq is not equal with gsi, they are in differentspaces, so pirq mapping fails.And in current linux codes, there is no method to get gsifor userspace.For above purpose, record gsi of pcistub devices when initpcistub and add a new syscall into privcmd to let userspacecan get gsi when they have a need.Signed-off-by: Jiqian Chen Signed-off-by: Huang Rui Signed-off-by: Jiqian Chen Reviewed-by: Stefano Stabellini Message-ID: <20240924061437.2636766-4-Jiqian.Chen@amd.com>Signed-off-by: Juergen Gross List of files: /linux-6.15/drivers/xen/Kconfig

de6c85bf - dma-mapping: clearly mark DMA ops as an architecture feature

Wed, 28 Aug 2024 06:02:47 +0000

dma-mapping: clearly mark DMA ops as an architecture featureDMA ops are a helper for architectures and not for drivers to overridethe DMA implementation.Unfortunately driver authors keep ignoring this. Make the fact moreclear by renaming the symbol to ARCH_HAS_DMA_OPS and having the two driversoverriding their dma_ops depend on that. These drivers should probably bemarked broken, but we can give them a bit of a grace period for that.Signed-off-by: Christoph Hellwig Reviewed-by: Thomas Gleixner Acked-by: Sakari Ailus # for IPU6Acked-by: Robin Murphy List of files: /linux-6.15/drivers/xen/Kconfig

f0d7db7b - xen: privcmd: Add support for ioeventfd

Mon, 16 Oct 2023 07:11:27 +0000

xen: privcmd: Add support for ioeventfdVirtio guests send VIRTIO_MMIO_QUEUE_NOTIFY notification when they needto notify the backend of an update to the status of the virtqueue. Thebackend or another entity, polls the MMIO address for updates to knowwhen the notification is sent.It works well if the backend does this polling by itself. But as we movetowards generic backend implementations, we end up implementing this ina separate user-space program.Generally, the Virtio backends are implemented to work with the Eventfdbased mechanism. In order to make such backends work with Xen, anothersoftware layer needs to do the polling and send an event via eventfd tothe backend once the notification from guest is received. This resultsin an extra context switch.This is not a new problem in Linux though. It is present with otherhypervisors like KVM, etc. as well. The generic solution implemented inthe kernel for them is to provide an IOCTL call to pass the address topoll and eventfd, which lets the kernel take care of polling and raisean event on the eventfd, instead of handling this in user space (whichinvolves an extra context switch).This patch adds similar support for xen.Inspired by existing implementations for KVM, etc..This also copies ioreq.h header file (only struct ioreq and relatedmacros) from Xen's source tree (Top commit 5d84f07fe6bf ("xen/pci: dropremaining uses of bool_t")).Signed-off-by: Viresh Kumar Reviewed-by: Juergen Gross Link: https://lore.kernel.org/r/b20d83efba6453037d0c099912813c79c81f7714.1697439990.git.viresh.kumar@linaro.orgSigned-off-by: Juergen Gross List of files: /linux-6.15/drivers/xen/Kconfig

f8941e6c - xen: privcmd: Add support for irqfd

Tue, 22 Aug 2023 09:45:07 +0000

xen: privcmd: Add support for irqfdXen provides support for injecting interrupts to the guests via theHYPERVISOR_dm_op() hypercall. The same is used by the Virtio baseddevice backend implementations, in an inefficient manner currently.Generally, the Virtio backends are implemented to work with the Eventfdbased mechanism. In order to make such backends work with Xen, anothersoftware layer needs to poll the Eventfds and raise an interrupt to theguest using the Xen based mechanism. This results in an extra contextswitch.This is not a new problem in Linux though. It is present with otherhypervisors like KVM, etc. as well. The generic solution implemented inthe kernel for them is to provide an IOCTL call to pass the interruptdetails and eventfd, which lets the kernel take care of polling theeventfd and raising of the interrupt, instead of handling this in userspace (which involves an extra context switch).This patch adds support to inject a specific interrupt to guest usingthe eventfd mechanism, by preventing the extra context switch.Inspired by existing implementations for KVM, etc..Signed-off-by: Viresh Kumar Reviewed-by: Juergen Gross Link: https://lore.kernel.org/r/8e724ac1f50c2bc1eb8da9b3ff6166f1372570aa.1692697321.git.viresh.kumar@linaro.orgSigned-off-by: Juergen Gross List of files: /linux-6.15/drivers/xen/Kconfig

7880672b - xen: Kconfig: Fix spelling mistake "Maxmium" -> "Maximum"

Fri, 07 Oct 2022 20:35:00 +0000

xen: Kconfig: Fix spelling mistake "Maxmium" -> "Maximum"There is a spelling mistake in a Kconfig description. Fix it.Signed-off-by: Colin Ian King Acked-by: Stefano Stabellini Link: https://lore.kernel.org/r/20221007203500.2756787-1-colin.i.king@gmail.comSigned-off-by: Juergen Gross List of files: /linux-6.15/drivers/xen/Kconfig

251e90e7 - xen: don't require virtio with grants for non-PV guests

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

xen: don't require virtio with grants for non-PV guestsCommit fa1f57421e0b ("xen/virtio: Enable restricted memory access usingXen grant mappings") introduced a new requirement for using virtiodevices: the backend now needs to support the VIRTIO_F_ACCESS_PLATFORMfeature.This is an undue requirement for non-PV guests, as those can be operatedwith existing backends without any problem, as long as those backendsare running in dom0.Per default allow virtio devices without grant support for non-PVguests.On Arm require VIRTIO_F_ACCESS_PLATFORM for devices having been listedin the device tree to use grants.Add a new config item to always force use of grants for virtio.Fixes: fa1f57421e0b ("xen/virtio: Enable restricted memory access using Xen grant mappings")Reported-by: Viresh Kumar Signed-off-by: Juergen Gross Reviewed-by: Oleksandr Tyshchenko Tested-by: Oleksandr Tyshchenko # Arm64 guest using XenReviewed-by: Stefano Stabellini Link: https://lore.kernel.org/r/20220622063838.8854-4-jgross@suse.comSigned-off-by: Juergen Gross List of files: /linux-6.15/drivers/xen/Kconfig

625ab90e - xen/grant-dma-ops: Retrieve the ID of backend's domain for DT devices

Thu, 02 Jun 2022 19:23:52 +0000

xen/grant-dma-ops: Retrieve the ID of backend's domain for DT devicesUse the presence of "iommus" property pointed to the IOMMU node withrecently introduced "xen,grant-dma" compatible as a clear indicatorof enabling Xen grant mappings scheme for that device and read the IDof Xen domain where the corresponding backend is running. The domid(domain ID) is used as an argument to the Xen grant mapping APIs.To avoid the deferred probe timeout which takes place after reusinggeneric IOMMU device tree bindings (because the IOMMU device neverbecomes available) enable recently introduced stub IOMMU driver byselecting XEN_GRANT_DMA_IOMMU.Also introduce xen_is_grant_dma_device() to check whether xen-grantDMA ops need to be set for a passed device.Remove the hardcoded domid 0 in xen_grant_setup_dma_ops().Signed-off-by: Oleksandr Tyshchenko Reviewed-by: Stefano Stabellini Link: https://lore.kernel.org/r/1654197833-25362-8-git-send-email-olekstysh@gmail.comSigned-off-by: Juergen Gross List of files: /linux-6.15/drivers/xen/Kconfig

1ca55d50 - xen/grant-dma-iommu: Introduce stub IOMMU driver

Thu, 02 Jun 2022 19:23:51 +0000

xen/grant-dma-iommu: Introduce stub IOMMU driverIn order to reuse generic IOMMU device tree bindings by Xen grantDMA-mapping layer we need to add this stub driver from a fw_devlinkperspective (grant-dma-ops cannot be converted into the properIOMMU driver).Otherwise, just reusing IOMMU bindings (without having a correspondingdriver) leads to the deferred probe timeout afterwards, becausethe IOMMU device never becomes available.This stub driver does nothing except registering empty iommu_ops,the upper layer "of_iommu" will treat this as NO_IOMMU conditionand won't return -EPROBE_DEFER.As this driver is quite different from the most hardware IOMMUimplementations and only needed in Xen guests, place it in drivers/xendirectory. The subsequent commit will make use of it.Signed-off-by: Oleksandr Tyshchenko Reviewed-by: Stefano Stabellini Link: https://lore.kernel.org/r/1654197833-25362-7-git-send-email-olekstysh@gmail.comSigned-off-by: Juergen Gross List of files: /linux-6.15/drivers/xen/Kconfig

fa1f5742 - xen/virtio: Enable restricted memory access using Xen grant mappings

Thu, 02 Jun 2022 19:23:49 +0000

xen/virtio: Enable restricted memory access using Xen grant mappingsIn order to support virtio in Xen guests add a config option XEN_VIRTIOenabling the user to specify whether in all Xen guests virtio shouldbe able to access memory via Xen grant mappings only on the host side.Also set PLATFORM_VIRTIO_RESTRICTED_MEM_ACCESS feature from the guestinitialization code on Arm and x86 if CONFIG_XEN_VIRTIO is enabled.Signed-off-by: Juergen Gross Signed-off-by: Oleksandr Tyshchenko Reviewed-by: Stefano Stabellini Reviewed-by: Boris Ostrovsky Link: https://lore.kernel.org/r/1654197833-25362-5-git-send-email-olekstysh@gmail.comSigned-off-by: Juergen Gross List of files: /linux-6.15/drivers/xen/Kconfig

d6aca350 - xen/grant-dma-ops: Add option to restrict memory access under Xen

Thu, 02 Jun 2022 19:23:48 +0000

xen/grant-dma-ops: Add option to restrict memory access under XenIntroduce Xen grant DMA-mapping layer which contains special DMA-mappingroutines for providing grant references as DMA addresses to be used byfrontends (e.g. virtio) in Xen guests.Add the needed functionality by providing a special set of DMA opshandling the needed grant operations for the I/O pages.The subsequent commit will introduce the use case for xen-grant DMA opslayer to enable using virtio devices in Xen guests in a safe manner.Signed-off-by: Juergen Gross Signed-off-by: Oleksandr Tyshchenko Reviewed-by: Stefano Stabellini Link: https://lore.kernel.org/r/1654197833-25362-4-git-send-email-olekstysh@gmail.comSigned-off-by: Juergen Gross List of files: /linux-6.15/drivers/xen/Kconfig

b2371587 - arm/xen: Read extended regions from DT and init Xen resource

Thu, 09 Dec 2021 20:05:35 +0000

arm/xen: Read extended regions from DT and init Xen resourceThis patch implements arch_xen_unpopulated_init() on Arm wherethe extended regions (if any) are gathered from DT and insertedinto specific Xen resource to be used as unused address spacefor Xen scratch pages by unpopulated-alloc code.The extended region (safe range) is a region of guest physicaladdress space which is unused and could be safely used to creategrant/foreign mappings instead of wasting real RAM pages fromthe domain memory for establishing these mappings.The extended regions are chosen by the hypervisor at the domaincreation time and advertised to it via "reg" property underhypervisor node in the guest device-tree. As region 0 is reservedfor grant table space (always present), the indexes for extendedregions are 1...N.If arch_xen_unpopulated_init() fails for some reason the defaultbehaviour will be restored (allocate xenballooned pages).This patch also removes XEN_UNPOPULATED_ALLOC dependency on x86.Signed-off-by: Oleksandr Tyshchenko Reviewed-by: Stefano Stabellini Link: https://lore.kernel.org/r/1639080336-26573-6-git-send-email-olekstysh@gmail.comSigned-off-by: Juergen Gross List of files: /linux-6.15/drivers/xen/Kconfig

897919ad - xen/privcmd: make option visible in Kconfig

Tue, 16 Nov 2021 14:33:23 +0000

xen/privcmd: make option visible in KconfigThis configuration option provides a misc device as an API to userspace.Make this API usable without having to select the module as a transitivedependency.This also fixes an issue where localyesconfig would selectCONFIG_XEN_PRIVCMD=m because it was not visible and defaulted tobuilding as module.[boris: clarified help message per Jan's suggestion]Based-on-patch-by: Thomas Weißschuh Signed-off-by: Juergen Gross Link: https://lore.kernel.org/r/20211116143323.18866-1-jgross@suse.comReviewed-by: Jan Beulich Reviewed-by: Thomas Weißschuh Signed-off-by: Boris Ostrovsky List of files: /linux-6.15/drivers/xen/Kconfig

a67efff2 - xen-pciback: allow compiling on other archs than x86

Thu, 28 Oct 2021 14:36:20 +0000

xen-pciback: allow compiling on other archs than x86Xen-pciback driver was designed to be built for x86 only. But itcan also be used by other architectures, e.g. Arm.Currently PCI backend implements multiple functionalities at a time,such as:1. It is used as a database for assignable PCI devices, e.g. xl pci-assignable-{add|remove|list} manipulates that list. So, whenever the toolstack needs to know which PCI devices can be passed through it reads that from the relevant sysfs entries of the pciback.2. It is used to hold the unbound PCI devices list, e.g. when passing through a PCI device it needs to be unbound from the relevant device driver and bound to pciback (strictly speaking it is not required that the device is bound to pciback, but pciback is again used as a database of the passed through PCI devices, so we can re-bind the devices back to their original drivers when guest domain shuts down)3. Device reset for the devices being passed through4. Para-virtualised use-cases supportThe para-virtualised part of the driver is not always needed as somearchitectures, e.g. Arm or x86 PVH Dom0, are not using backend-frontendmodel for PCI device passthrough.For such use-cases make the very first step in splitting thexen-pciback driver into two parts: Xen PCI stub and PCI PV backenddrivers.For that add new configuration options CONFIG_XEN_PCI_STUB andCONFIG_XEN_PCIDEV_STUB, so the driver can be limited in itsfunctionality, e.g. no support for para-virtualised scenario.x86 platform will continue using CONFIG_XEN_PCIDEV_BACKEND for thefully featured backend driver.Signed-off-by: Oleksandr Andrushchenko Signed-off-by: Anastasiia Lukianenko Reviewed-by: Stefano Stabellini Reviewed-by: Juergen Gross Link: https://lore.kernel.org/r/20211028143620.144936-1-andr2000@gmail.comSigned-off-by: Boris Ostrovsky List of files: /linux-6.15/drivers/xen/Kconfig

cae7d81a - xen/x86: allow PVH Dom0 without XEN_PV=y

Thu, 30 Sep 2021 12:16:47 +0000

xen/x86: allow PVH Dom0 without XEN_PV=yDecouple XEN_DOM0 from XEN_PV, converting some existing uses of XEN_DOM0to a new XEN_PV_DOM0. (I'm not convinced all are really / should reallybe PV-specific, but for starters I've tried to be conservative.)For PVH Dom0 the hypervisor populates MADT with only x2APIC entries, sowithout x2APIC support enabled in the kernel things aren't going to workvery well. (As opposed, DomU-s would only ever see LAPIC entries in MADTas of now.) Note that this then requires PVH Dom0 to be 64-bit, asX86_X2APIC depends on X86_64.In the course of this xen_running_on_version_or_later() needs to beavailable more broadly. Move it from a PV-specific to a generic file,considering that what it does isn't really PV-specific at all anyway.Note that xen/interface/version.h cannot be included on its own; inenlighten.c, which uses SCHEDOP_* anyway, include xen/interface/sched.hfirst to resolve the apparently sole missing type (xen_ulong_t).Signed-off-by: Jan Beulich Reviewed-by: Juergen Gross Link: https://lore.kernel.org/r/983bb72f-53df-b6af-14bd-5e088bd06a08@suse.comSigned-off-by: Juergen Gross List of files: /linux-6.15/drivers/xen/Kconfig

794d5b8a - swiotlb-xen: this is PV-only on x86

Fri, 17 Sep 2021 10:50:38 +0000

swiotlb-xen: this is PV-only on x86The code is unreachable for HVM or PVH, and it also makes little sensein auto-translated environments. On Arm, withxen_{create,destroy}_contiguous_region() both being stubs, I have a hardtime seeing what good the Xen specific variant does - the generic oneought to be fine for all purposes there. Still Arm code explicitlyreferences symbols here, so the code will continue to be included there.Instead of making PCI_XEN's "select" conditional, simply drop it -SWIOTLB_XEN will be available unconditionally in the PV case anyway, andis - as explained above - dead code in non-PV environments.This in turn allows dropping the stubs forxen_{create,destroy}_contiguous_region(), the former of which was brokenanyway - it failed to set the DMA handle output.Signed-off-by: Jan Beulich Reviewed-by: Christoph Hellwig Reviewed-by: Stefano Stabellini Link: https://lore.kernel.org/r/5947b8ae-fdc7-225c-4838-84712265fc1e@suse.comSigned-off-by: Juergen Gross List of files: /linux-6.15/drivers/xen/Kconfig

45da2344 - xen/pvcalls: backend can be a module

Tue, 07 Sep 2021 12:17:13 +0000

xen/pvcalls: backend can be a moduleIt's not clear to me why only the frontend has been tristate. Switch thebackend to be, too.Signed-off-by: Jan Beulich Acked-by: Stefano Stabellini Link: https://lore.kernel.org/r/54a6070c-92bb-36a3-2fc0-de9ccca438c5@suse.comSigned-off-by: Juergen Gross List of files: /linux-6.15/drivers/xen/Kconfig

01325044 - xen: Remove support for PV ACPI cpu/memory hotplug

Tue, 13 Apr 2021 17:52:24 +0000

xen: Remove support for PV ACPI cpu/memory hotplugCommit 76fc253723ad ("xen/acpi-stub: Disable it b/c the acpi_processor_addis no longer called.") declared as BROKEN support for Xen ACPI stub (whichis required for xen-acpi-{cpu|memory}-hotplug) and suggested that thisis temporary and will be soon fixed. This was in March 2013.Further, commit cfafae940381 ("xen: rename dom0_op to platform_op")renamed an interface used by memory hotplug code without updating thatcode (as it was BROKEN and therefore not compiled). This wasin November 2015 and has gone unnoticed for over 5 year.It is now clear that this code is of no interest to anyone and thereforeshould be removed.Signed-off-by: Boris Ostrovsky Acked-by: Rafael J. Wysocki Link: https://lore.kernel.org/r/1618336344-3162-1-git-send-email-boris.ostrovsky@oracle.comSigned-off-by: Juergen Gross List of files: /linux-6.15/drivers/xen/Kconfig