Changes in Makefile

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

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

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

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

34aff145 - xen: Remove Xen PVH/PVHVM dependency on PCI

Wed, 14 Oct 2020 17:53:40 +0000

xen: Remove Xen PVH/PVHVM dependency on PCIA Xen PVH domain doesn't have a PCI bus or devices, so it doesn't needPCI support built in. Currently, XEN_PVH depends on XEN_PVHVM whichdepends on PCI.Introduce XEN_PVHVM_GUEST as a toplevel item and change XEN_PVHVM to ahidden variable. This allows XEN_PVH to depend on XEN_PVHVM without PCIwhile XEN_PVHVM_GUEST depends on PCI.In drivers/xen, compile platform-pci depending on XEN_PVHVM_GUEST sincethat pulls in the PCI dependency for linking.Signed-off-by: Jason Andryuk Reviewed-by: Juergen Gross Link: https://lore.kernel.org/r/20201014175342.152712-2-jandryuk@gmail.comSigned-off-by: Juergen Gross List of files: /linux-6.15/drivers/xen/Makefile

9e2369c0 - xen: add helpers to allocate unpopulated memory

Tue, 01 Sep 2020 08:33:26 +0000

xen: add helpers to allocate unpopulated memoryTo be used in order to create foreign mappings. This is based on theZONE_DEVICE facility which is used by persistent memory devices inorder to create struct pages and kernel virtual mappings for the IOMEMareas of such devices. Note that on kernels without support forZONE_DEVICE Xen will fallback to use ballooned pages in order tocreate foreign mappings.The newly added helpers use the same parameters as the existing{alloc/free}_xenballooned_pages functions, which allows for in-placereplacement of the callers. Once a memory region has been added to beused as scratch mapping space it will no longer be released, and pagesreturned are kept in a linked list. This allows to have a buffer ofpages and prevents resorting to frequent additions and removals ofregions.If enabled (because ZONE_DEVICE is supported) the usage of the newfunctionality untangles Xen balloon and RAM hotplug from the usage ofunpopulated physical memory ranges to map foreign pages, which is thecorrect thing to do in order to avoid mappings of foreign pages dependon memory hotplug.Note the driver is currently not enabled on Arm platforms because itwould interfere with the identity mapping required on some platforms.Signed-off-by: Roger Pau Monné Reviewed-by: Juergen Gross Link: https://lore.kernel.org/r/20200901083326.21264-4-roger.pau@citrix.comSigned-off-by: Juergen Gross List of files: /linux-6.15/drivers/xen/Makefile

893ab004 - kbuild: remove cc-option test of -fno-stack-protector

Fri, 26 Jun 2020 18:59:12 +0000

kbuild: remove cc-option test of -fno-stack-protectorSome Makefiles already pass -fno-stack-protector unconditionally.For example, arch/arm64/kernel/vdso/Makefile, arch/x86/xen/Makefile.No problem report so far about hard-coding this option. So, we canassume all supported compilers know -fno-stack-protector.GCC 4.8 and Clang support this option (https://godbolt.org/z/_HDGzN)Get rid of cc-option from -fno-stack-protector.Remove CONFIG_CC_HAS_STACKPROTECTOR_NONE, which is always 'y'.Note:arch/mips/vdso/Makefile adds -fno-stack-protector twice, firstunconditionally, and second conditionally. I removed the second one.Signed-off-by: Masahiro Yamada Reviewed-by: Kees Cook Acked-by: Ard Biesheuvel Reviewed-by: Nick Desaulniers List of files: /linux-6.15/drivers/xen/Makefile

2f6474e4 - x86/entry: Switch XEN/PV hypercall entry to IDTENTRY

Thu, 21 May 2020 20:05:26 +0000

x86/entry: Switch XEN/PV hypercall entry to IDTENTRYConvert the XEN/PV hypercall to IDTENTRY: - Emit the ASM stub with DECLARE_IDTENTRY - Remove the ASM idtentry in 64-bit - Remove the open coded ASM entry code in 32-bit - Remove the old prototypesThe handler stubs need to stay in ASM code as they need corner case handlingand adjustment of the stack pointer.Provide a new C function which invokes the entry/exit handling and callsinto the XEN handler on the interrupt stack if required.The exit code is slightly different from the regular idtentry_exit() onnon-preemptible kernels. If the hypercall is preemptible and need_resched()is set then XEN provides a preempt hypercall scheduling function.Move this functionality into the entry code so it can use the existingidtentry functionality.[ mingo: Build fixes. ]Signed-off-by: Thomas Gleixner Signed-off-by: Ingo Molnar Acked-by: Andy Lutomirski Acked-by: Juergen Gross Tested-by: Juergen Gross Link: https://lore.kernel.org/r/20200521202118.055270078@linutronix.de List of files: /linux-6.15/drivers/xen/Makefile

814bbf49 - xen: remove tmem driver

Sun, 14 Jul 2019 12:04:14 +0000

xen: remove tmem driverThe Xen tmem (transcendent memory) driver can be removed, as therelated Xen hypervisor feature never made it past the "experimental"state and will be removed in future Xen versions (>= 4.13).The xen-selfballoon driver depends on tmem, so it can be removed, too.Signed-off-by: Juergen Gross Acked-by: Boris Ostrovsky Signed-off-by: Juergen Gross List of files: /linux-6.15/drivers/xen/Makefile

b1ddd406 - xen: remove pre-xen3 fallback handlers

Mon, 04 Mar 2019 20:52:39 +0000

xen: remove pre-xen3 fallback handlersThe legacy hypercall handlers were originally added witha comment explaining that "copying the argument structures inHYPERVISOR_event_channel_op() and HYPERVISOR_physdev_op() into the localvariable is sufficiently safe" and only made sure to not writepast the end of the argument structure, the checks in linux/string.hdisagree with that, when link-time optimizations are used:In function 'memcpy', inlined from 'pirq_query_unmask' at drivers/xen/fallback.c:53:2, inlined from '__startup_pirq' at drivers/xen/events/events_base.c:529:2, inlined from 'restore_pirqs' at drivers/xen/events/events_base.c:1439:3, inlined from 'xen_irq_resume' at drivers/xen/events/events_base.c:1581:2:include/linux/string.h:350:3: error: call to '__read_overflow2' declared with attribute error: detected read beyond size of object passed as 2nd parameter __read_overflow2(); ^Further research turned out that only Xen 3.0.2 or earlier required thefallback at all, while all versions in use today don't need it.As far as I can tell, it is not even possible to run a mainline kernelon those old Xen releases, at the time when they were in use, onlya patched kernel was supported anyway.Fixes: cf47a83fb06e ("xen/hypercall: fix hypercall fallback code for very old hypervisors")Reviewed-by: Boris Ostrovsky Cc: Jan Beulich Signed-off-by: Arnd Bergmann Signed-off-by: Juergen Gross List of files: /linux-6.15/drivers/xen/Makefile

b3383974 - xen: Introduce shared buffer helpers for page directory...

Fri, 30 Nov 2018 07:42:03 +0000

xen: Introduce shared buffer helpers for page directory...based frontends. Currently the frontends which implementsimilar code for sharing big buffers between frontend andbackend are para-virtualized DRM and sound drivers.Both define the same way to share grant references of adata buffer with the corresponding backend with littledifferences.Move shared code into a helper module, so there is a singleimplementation of the same functionality for all.This patch introduces code which is used by sound and displayfrontend drivers without functional changes with the intentionto remove shared code from the corresponding drivers.Signed-off-by: Oleksandr Andrushchenko Acked-by: Boris Ostrovsky Signed-off-by: Boris Ostrovsky List of files: /linux-6.15/drivers/xen/Makefile

932d6562 - xen/gntdev: Add initial support for dma-buf UAPI

Fri, 20 Jul 2018 09:01:48 +0000

xen/gntdev: Add initial support for dma-buf UAPIAdd UAPI and IOCTLs for dma-buf grant device driver extension:the extension allows userspace processes and kernel modules touse Xen backed dma-buf implementation. With this extension grantreferences to the pages of an imported dma-buf can be exportedfor other domain use and grant references coming from a foreigndomain can be converted into a local dma-buf for local export.Implement basic initialization and stubs for Xen DMA buffers'support.Signed-off-by: Oleksandr Andrushchenko Reviewed-by: Boris Ostrovsky Signed-off-by: Boris Ostrovsky List of files: /linux-6.15/drivers/xen/Makefile

ae4c51a5 - xen/balloon: Share common memory reservation routines

Fri, 20 Jul 2018 09:01:44 +0000

xen/balloon: Share common memory reservation routinesMemory {increase|decrease}_reservation and VA mappings update/resetcode used in balloon driver can be made common, so other drivers canalso re-use the same functionality without open-coding.Create a dedicated file for the shared code and export correspondingsymbols for other kernel modules.Signed-off-by: Oleksandr Andrushchenko Reviewed-by: Boris Ostrovsky Signed-off-by: Boris Ostrovsky List of files: /linux-6.15/drivers/xen/Makefile

c51b3c63 - xen: add new hypercall buffer mapping device

Mon, 18 Jun 2018 07:36:39 +0000

xen: add new hypercall buffer mapping deviceFor passing arbitrary data from user land to the Xen hypervisor theXen tools today are using mlock()ed buffers. Unfortunately the kernelmight change access rights of such buffers for brief periods of timee.g. for page migration or compaction, leading to access faults in thehypervisor, as the hypervisor can't use the locks of the kernel.In order to solve this problem add a new device node to the Xen privcmddriver to easily allocate hypercall buffers via mmap(). The memory isallocated in the kernel and just mapped into user space. Marked asVM_IO the user mapping will not be subject to page migration et al.Signed-off-by: Juergen Gross Reviewed-by: Boris Ostrovsky Signed-off-by: Juergen Gross List of files: /linux-6.15/drivers/xen/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/xen/Makefile

5eee149a - xen: introduce a Kconfig option to enable the pvcalls frontend

Mon, 30 Oct 2017 22:41:03 +0000

xen: introduce a Kconfig option to enable the pvcalls frontendAlso add pvcalls-front to the Makefile.Signed-off-by: Stefano Stabellini Reviewed-by: Boris Ostrovsky CC: boris.ostrovsky@oracle.comCC: jgross@suse.comSigned-off-by: Boris Ostrovsky List of files: /linux-6.15/drivers/xen/Makefile

42d3078a - xen: introduce a Kconfig option to enable the pvcalls backend

Thu, 06 Jul 2017 18:01:08 +0000

xen: introduce a Kconfig option to enable the pvcalls backendAlso add pvcalls-back to the Makefile.Signed-off-by: Stefano Stabellini Reviewed-by: Juergen Gross CC: boris.ostrovsky@oracle.comCC: jgross@suse.comSigned-off-by: Boris Ostrovsky List of files: /linux-6.15/drivers/xen/Makefile

8c97023c - Kbuild: use -fshort-wchar globally

Wed, 26 Jul 2017 13:36:23 +0000

Kbuild: use -fshort-wchar globallyCommit 971a69db7dc0 ("Xen: don't warn about 2-byte wchar_t in efi")added the --no-wchar-size-warning to the Makefile to avoid thisharmless warning:arm-linux-gnueabi-ld: warning: drivers/xen/efi.o uses 2-byte wchar_t yet the output is to use 4-byte wchar_t; use of wchar_t values across objects may failChanging kbuild to use thin archives instead of recursive linkingunfortunately brings the same warning back during the final link.The kernel does not use wchar_t string literals at this point, andxen does not use wchar_t at all (only efi_char16_t), so the flaghas no effect, but as pointed out by Jan Beulich, adding a wchar_tstring literal would be bad here.Since wchar_t is always defined as u16, independent of the toolchaindefault, always passing -fshort-wchar is correct and lets usremove the Xen specific hack along with fixing the warning.Link: https://patchwork.kernel.org/patch/9275217/Fixes: 971a69db7dc0 ("Xen: don't warn about 2-byte wchar_t in efi")Signed-off-by: Arnd Bergmann Acked-by: David Vrabel Signed-off-by: Masahiro Yamada List of files: /linux-6.15/drivers/xen/Makefile

4ba04bec - Xen: ARM: Add support for mapping platform device mmio

Thu, 07 Apr 2016 12:03:23 +0000

Xen: ARM: Add support for mapping platform device mmioAdd a bus_notifier for platform bus device in order to map the devicemmio regions when DOM0 booting with ACPI.Signed-off-by: Shannon Zhao Acked-by: Stefano Stabellini Tested-by: Julien Grall List of files: /linux-6.15/drivers/xen/Makefile

971a69db - Xen: don't warn about 2-byte wchar_t in efi

Wed, 11 May 2016 12:47:59 +0000

Xen: don't warn about 2-byte wchar_t in efiThe XEN UEFI code has become available on the ARM architecturerecently, but now causes a link-time warning:ld: warning: drivers/xen/efi.o uses 2-byte wchar_t yet the output is to use 4-byte wchar_t; use of wchar_t values across objects may failThis seems harmless, because the efi code only uses 2-bytecharacters when interacting with EFI, so we don't pass on thosestrings to elsewhere in the system, and we just need tosilence the warning.It is not clear to me whether we actually need to build the filewith the -fshort-wchar flag, but if we do, then we should alsopass --no-wchar-size-warning to the linker, to avoid the warning.Signed-off-by: Arnd Bergmann Reviewed-by: Stefano Stabellini Fixes: 37060935dc04 ("ARM64: XEN: Add a function to initialize Xen specific UEFI runtime services") List of files: /linux-6.15/drivers/xen/Makefile