Changes in Makefile

5a0fcb0e - cxl: Remove driver

Wed, 19 Feb 2025 07:00:06 +0000

cxl: Remove driverRemove the cxl driver that provides support for the IBM CoherentAccelerator Processor Interface. Revert or clean up associated code inarch/powerpc that is no longer necessary.cxl has received minimal maintenance for several years, and is notsupported on the Power10 processor. We aren't aware of any users who arelikely to be using recent kernels.Thanks to Mikey Neuling, Ian Munsie, Daniel Axtens, Frederic Barrat,Christophe Lombard, Philippe Bergheaud, Vaibhav Jain and AlastairD'Silva for their work on this driver over the years.Signed-off-by: Andrew Donnellan Acked-by: Frederic Barrat Acked-by: Madhavan Srinivasan Signed-off-by: Michael Ellerman Link: https://patch.msgid.link/20250219070007.177725-2-ajd@linux.ibm.com List of files: /linux-6.15/arch/powerpc/platforms/powernv/Makefile

743cdb7b - powerpc/kasan: Mark more real-mode code as not to be instrumented

Thu, 19 May 2022 07:45:21 +0000

powerpc/kasan: Mark more real-mode code as not to be instrumentedThis marks more files and functions that can possibly be called inreal mode as not to be instrumented by KASAN. Most were found byinspection, except for get_pseries_errorlog() which was reported ascausing a crash in testing.Reported-by: Nageswara R Sastry Signed-off-by: Paul Mackerras Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/YoX1kZPnmUX4RZEK@cleo List of files: /linux-6.15/arch/powerpc/platforms/powernv/Makefile

41b7a347 - powerpc: Book3S 64-bit outline-only KASAN support

Wed, 18 May 2022 10:05:31 +0000

powerpc: Book3S 64-bit outline-only KASAN supportImplement a limited form of KASAN for Book3S 64-bit machines running underthe Radix MMU, supporting only outline mode. - Enable the compiler instrumentation to check addresses and maintain the shadow region. (This is the guts of KASAN which we can easily reuse.) - Require kasan-vmalloc support to handle modules and anything else in vmalloc space. - KASAN needs to be able to validate all pointer accesses, but we can't instrument all kernel addresses - only linear map and vmalloc. On boot, set up a single page of read-only shadow that marks all iomap and vmemmap accesses as valid. - Document KASAN in powerpc docs.Background----------KASAN support on Book3S is a bit tricky to get right: - It would be good to support inline instrumentation so as to be able to catch stack issues that cannot be caught with outline mode. - Inline instrumentation requires a fixed offset. - Book3S runs code with translations off ("real mode") during boot, including a lot of generic device-tree parsing code which is used to determine MMU features. [ppc64 mm note: The kernel installs a linear mapping at effective address c000...-c008.... This is a one-to-one mapping with physical memory from 0000... onward. Because of how memory accesses work on powerpc 64-bit Book3S, a kernel pointer in the linear map accesses the same memory both with translations on (accessing as an 'effective address'), and with translations off (accessing as a 'real address'). This works in both guests and the hypervisor. For more details, see s5.7 of Book III of version 3 of the ISA, in particular the Storage Control Overview, s5.7.3, and s5.7.5 - noting that this KASAN implementation currently only supports Radix.] - Some code - most notably a lot of KVM code - also runs with translations off after boot. - Therefore any offset has to point to memory that is valid with translations on or off.One approach is just to give up on inline instrumentation. This wayboot-time checks can be delayed until after the MMU is set is up, and wecan just not instrument any code that runs with translations off afterbooting. Take this approach for now and require outline instrumentation.Previous attempts allowed inline instrumentation. However, they came withsome unfortunate restrictions: only physically contiguous memory could beused and it had to be specified at compile time. Maybe we can do better inthe future.[paulus@ozlabs.org - Rebased onto 5.17. Note that a kernel with CONFIG_KASAN=y will crash during boot on a machine using HPT translation because not all the entry points to the generic KASAN code are protected with a call to kasan_arch_is_ready().]Originally-by: Balbir Singh # ppc64 out-of-line radix versionSigned-off-by: Daniel Axtens Signed-off-by: Paul Mackerras [mpe: Update copyright year and comment formatting]Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/YoTE69OQwiG7z+Gu@cleo List of files: /linux-6.15/arch/powerpc/platforms/powernv/Makefile

413d6ed3 - powerpc/vas: Move VAS API to book3s common platform

Thu, 17 Jun 2021 20:29:48 +0000

powerpc/vas: Move VAS API to book3s common platformThe pseries platform will share vas and nx code and interfaceswith the PowerNV platform, so create thearch/powerpc/platforms/book3s/ directory and move VAS API codethere. Functionality is not changed.Signed-off-by: Haren Myneni Reviewed-by: Nicholas Piggin Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/e05c8db17b9eabe3545b902d034238e4c6c08180.camel@linux.ibm.com List of files: /linux-6.15/arch/powerpc/platforms/powernv/Makefile

562d1e20 - powerpc/powernv: remove the nvlink support

Fri, 26 Mar 2021 06:13:11 +0000

powerpc/powernv: remove the nvlink supportThis code was only used by the vfio-nvlink2 code, which itself had noproper use. Drop this huge chunk of code build into every powernvor generic build.Signed-off-by: Christoph Hellwig Acked-by: Greg Kroah-Hartman Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20210326061311.1497642-3-hch@lst.de List of files: /linux-6.15/arch/powerpc/platforms/powernv/Makefile

37b59ef0 - powerpc/powernv/sriov: Move SR-IOV into a separate file

Wed, 22 Jul 2020 06:57:04 +0000

powerpc/powernv/sriov: Move SR-IOV into a separate filepci-ioda.c is getting a bit unwieldly due to the amount of stuff jammed inthere. The SR-IOV support can be extracted easily enough and is mostlystandalone, so move it into a separate file.This patch also moves the PowerNV SR-IOV specific fields from pci_dn andmoves them into a platform specific structure. I'm not sure how they endedup in there in the first place, but leaking platform specifics into commoncode has proven to be a terrible idea so far so lets stop doing that.Signed-off-by: Oliver O'Halloran Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20200722065715.1432738-5-oohall@gmail.com List of files: /linux-6.15/arch/powerpc/platforms/powernv/Makefile

dda44eb2 - powerpc/vas: Add VAS user space API

Fri, 17 Apr 2020 09:02:01 +0000

powerpc/vas: Add VAS user space APIOn power9, userspace can send GZIP compression requests directly to NXonce kernel establishes NX channel / window with VAS. This patch providesuser space API which allows user space to establish channel using openVAS_TX_WIN_OPEN ioctl, mmap and close operations.Each window corresponds to file descriptor and application can openmultiple windows. After the window is opened, VAS_TX_WIN_OPEN icoctl toopen a window on specific VAS instance, mmap() system call to mapthe hardware address of engine's request queue into the application'svirtual address space.Then the application can then submit one or more requests to the theengine by using the copy/paste instructions and pasting the CRBs tothe virtual address (aka paste_address) returned by mmap().Only NX GZIP coprocessor type is supported right now and allow GZIPengine access via /dev/crypto/nx-gzip device node.Thanks to Michael Ellerman for his changes and suggestions to make theioctl generic to support any coprocessor type.Signed-off-by: Sukadev Bhattiprolu Signed-off-by: Haren Myneni Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/1587114121.2275.1109.camel@hbabu-laptop List of files: /linux-6.15/arch/powerpc/platforms/powernv/Makefile

0d17de03 - powerpc/vas: Setup fault window per VAS instance

Thu, 16 Apr 2020 06:00:46 +0000

powerpc/vas: Setup fault window per VAS instanceSetup fault window for each VAS instance. When NX gets a fault onrequest buffer, pastes fault CRB in the corresponding fault FIFO andthen raises an interrupt to the OS. The kernel handles this faultand process faults CRB from this FIFO.Signed-off-by: Sukadev Bhattiprolu Signed-off-by: Haren Myneni Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/1587016846.2275.1053.camel@hbabu-laptop List of files: /linux-6.15/arch/powerpc/platforms/powernv/Makefile

9155e234 - powerpc/powernv: Add OPAL API interface to access secure variable

Mon, 11 Nov 2019 03:10:33 +0000

powerpc/powernv: Add OPAL API interface to access secure variableThe X.509 certificates trusted by the platform and required to secureboot the OS kernel are wrapped in secure variables, which arecontrolled by OPAL.This patch adds firmware/kernel interface to read and write OPALsecure variables based on the unique key.This support can be enabled using CONFIG_OPAL_SECVAR.Signed-off-by: Claudio Carvalho Signed-off-by: Nayna Jain Signed-off-by: Eric Richter [mpe: Make secvar_ops __ro_after_init, only build opal-secvar.c if PPC_SECURE_BOOT=y]Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/1573441836-3632-2-git-send-email-nayna@linux.ibm.com List of files: /linux-6.15/arch/powerpc/platforms/powernv/Makefile

6f713d18 - powerpc/opalcore: export /sys/firmware/opal/core for analysing opal crashes

Wed, 11 Sep 2019 14:56:33 +0000

powerpc/opalcore: export /sys/firmware/opal/core for analysing opal crashesExport /sys/firmware/opal/core file to analyze opal crashes. Since OPALcore can be generated independent of CONFIG_FA_DUMP support in kernel,add this support under a new kernel config option CONFIG_OPAL_CORE.Also, avoid code duplication by moving common code used while exporting/proc/vmcore and/or /sys/firmware/opal/core file(s).Signed-off-by: Hari Bathini Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/156821378503.5656.3693769384945087756.stgit@hbathini.in.ibm.com List of files: /linux-6.15/arch/powerpc/platforms/powernv/Makefile

bec53196 - powerpc/fadump: add support to preserve crash data on FADUMP disabled kernel

Wed, 11 Sep 2019 14:56:03 +0000

powerpc/fadump: add support to preserve crash data on FADUMP disabled kernelAdd a new kernel config option, CONFIG_PRESERVE_FA_DUMP that ensuresthat crash data, from previously crash'ed kernel, is preserved. Thishelps in cases where FADump is not enabled but the subsequent memorypreserving kernel boot is likely to process this crash data. Onetypical usecase for this config option is petitboot kernel.As OPAL allows registering address with it in the first kernel andretrieving it after MPIPL, use it to store the top of boot memory.A kernel that intends to preserve crash data retrieves it and avoidsusing memory beyond this address.Move arch_reserved_kernel_pages() function as it is needed for bothFA_DUMP and PRESERVE_FA_DUMP configurations.Signed-off-by: Hari Bathini Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/156821375751.5656.11459483669542541602.stgit@hbathini.in.ibm.com List of files: /linux-6.15/arch/powerpc/platforms/powernv/Makefile

41df5928 - powerpc/fadump: add fadump support on powernv

Wed, 11 Sep 2019 14:50:26 +0000

powerpc/fadump: add fadump support on powernvAdd basic callback functions for FADump on PowerNV platform.Signed-off-by: Hari Bathini Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/156821342072.5656.4346362203141486452.stgit@hbathini.in.ibm.com List of files: /linux-6.15/arch/powerpc/platforms/powernv/Makefile

bb04ffe8 - powerpc/powernv: Introduce FW_FEATURE_ULTRAVISOR

Thu, 22 Aug 2019 03:48:34 +0000

powerpc/powernv: Introduce FW_FEATURE_ULTRAVISORIn PEF enabled systems, some of the resources which were previouslyhypervisor privileged are now ultravisor privileged and controlled bythe ultravisor firmware.This adds FW_FEATURE_ULTRAVISOR to indicate if PEF is enabled.The host kernel can use FW_FEATURE_ULTRAVISOR, for instance, to skipaccessing resources (e.g. PTCR and LDBAR) in case PEF is enabled.Signed-off-by: Claudio Carvalho [ andmike: Device node name to "ibm,ultravisor" ]Signed-off-by: Michael Anderson Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20190822034838.27876-4-cclaudio@linux.ibm.com List of files: /linux-6.15/arch/powerpc/platforms/powernv/Makefile

bfd2f0d4 - powerpc/powernv: Get rid of old scom_controller abstraction

Thu, 09 May 2019 05:11:17 +0000

powerpc/powernv: Get rid of old scom_controller abstractionOnce upon a time, the SCOM access code was used by the WSP platform aswell as powernv. Thus it made sense to have a generic SCOM accessinterface to abstract between different platforms.Now that it's just powernv, with no other platforms currently on thehorizon, let's rip out scom_controller and make everything muchsimpler and more direct.While we're here, fix up the comment block at the top.Signed-off-by: Andrew Donnellan Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20190509051119.7694-3-ajd@linux.ibm.com List of files: /linux-6.15/arch/powerpc/platforms/powernv/Makefile

08a456aa - powerpc/powernv: Move SCOM access code into powernv platform

Thu, 09 May 2019 05:11:15 +0000

powerpc/powernv: Move SCOM access code into powernv platformThe powernv platform is the only one that directly accesses SCOMs.Move the support code to platforms/powernv, and get rid of thePPC_SCOM Kconfig option, as SCOM support is always selected whencompiling for powernv.This also means that the Kconfig item for CONFIG_SCOM_DEBUGFS willshow up in menuconfig in the platform menu, rather than at the root,which is a much better location.Signed-off-by: Andrew Donnellan Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20190509051119.7694-1-ajd@linux.ibm.com List of files: /linux-6.15/arch/powerpc/platforms/powernv/Makefile

75d9fc7f - powerpc/powernv: move OPAL call wrapper tracing and interrupt handling to C

Tue, 26 Feb 2019 09:30:35 +0000

powerpc/powernv: move OPAL call wrapper tracing and interrupt handling to CThe OPAL call wrapper gets interrupt disabling wrong. It disablesinterrupts just by clearing MSR[EE], which has two problems:- It doesn't call into the IRQ tracing subsystem, which means tracing across OPAL calls does not always notice IRQs have been disabled.- It doesn't go through the IRQ soft-mask code, which causes a minor bug. MSR[EE] can not be restored by saving the MSR then clearing MSR[EE], because a racing interrupt while soft-masked could clear MSR[EE] between the two steps. This can cause MSR[EE] to be incorrectly enabled when the OPAL call returns. Fortunately that should only result in another masked interrupt being taken to disable MSR[EE] again, but it's a bit sloppy.The existing code also saves MSR to PACA, which is not re-entrant ifthere is a nested OPAL call from different MSR contexts, which canhappen these days with SRESET interrupts on bare metal.To fix these issues, move the tracing and IRQ handling code to C, andcall into asm just for the low level call when everything is ready togo. Save the MSR on stack rather than PACA.Performance cost is kept to a minimum with a few optimisations:- The endian switch upon return is combined with the MSR restore, which avoids an expensive context synchronizing operation for LE kernels. This makes up for the additional mtmsrd to enable interrupts with local_irq_enable().- blr is now used to return from the opal_* functions that are called as C functions, to avoid link stack corruption. This requires a skiboot fix as well to keep the call stack balanced.A NULL call is more costly after this, (410ns->430ns on POWER9), butOPAL calls are generally not performance critical at this scale.Signed-off-by: Nicholas Piggin Signed-off-by: Michael Ellerman List of files: /linux-6.15/arch/powerpc/platforms/powernv/Makefile

191c2287 - powerpc/powernv: Move TCE manupulation code to its own file

Wed, 04 Jul 2018 06:13:45 +0000

powerpc/powernv: Move TCE manupulation code to its own fileRight now we have allocation code in pci-ioda.c and traversing code inpci.c, let's keep them toghether. However both files are big enoughalready so let's move this business to a new file.While we at it, move the code which links IOMMU table groups toIOMMU tables as it is not specific to any PNV PHB model.These puts exported symbols from the new file together.This fixes several warnings from checkpatch.pl like this:"WARNING: Prefer 'unsigned int' to bare use of 'unsigned'".As this is almost cut-n-paste, there should be no behavioral change.Reviewed-by: David Gibson Signed-off-by: Alexey Kardashevskiy Signed-off-by: Michael Ellerman List of files: /linux-6.15/arch/powerpc/platforms/powernv/Makefile

2f65272a - powerpc/powernv/vas: Remove a stray line in Makefile

Wed, 17 Jan 2018 02:50:39 +0000

powerpc/powernv/vas: Remove a stray line in MakefileRemove a bogus line from arch/powerpc/platforms/powernv/Makefile thatwas added by commit ece4e51 ("powerpc/vas: Export HVWC to debugfs").Signed-off-by: Sukadev Bhattiprolu Signed-off-by: Michael Ellerman List of files: /linux-6.15/arch/powerpc/platforms/powernv/Makefile

6914c757 - powerpc/powernv: Add platform-specific services for opencapi

Tue, 23 Jan 2018 11:31:39 +0000

powerpc/powernv: Add platform-specific services for opencapiImplement a few platform-specific calls which can be used by drivers:- provide the Transaction Layer capabilities of the host, so that the driver can find some common ground and configure the device and host appropriately.- provide the hw interrupt to be used for translation faults raised by the NPU- map/unmap some NPU mmio registers to get the fault context when the NPU raises an address translation faultThe rest are wrappers around the previously-introduced opal calls.Signed-off-by: Frederic Barrat Signed-off-by: Michael Ellerman List of files: /linux-6.15/arch/powerpc/platforms/powernv/Makefile

ece4e512 - powerpc/vas: Export HVWC to debugfs

Wed, 08 Nov 2017 02:23:51 +0000

powerpc/vas: Export HVWC to debugfsExport the VAS Window context information to debugfs.We need to hold a mutex when closing the window to prevent a racewith the debugfs read(). Rather than introduce a per-instance mutex,we use the global vas_mutex for now, since it is not heavily contended.The window->cop field is only relevant to a receive window so we werenot setting it for a send window (which is is paired to a receive windowanyway). But to simplify reporting in debugfs, set the 'cop' field for thesend window also.Signed-off-by: Sukadev Bhattiprolu Signed-off-by: Michael Ellerman List of files: /linux-6.15/arch/powerpc/platforms/powernv/Makefile