Changes in Kconfig

8e80a73f - powerpc/xive: Change IRQ domain to a tree domain

Tue, 16 Nov 2021 13:40:22 +0000

powerpc/xive: Change IRQ domain to a tree domainCommit 4f86a06e2d6e ("irqdomain: Make normal and nomap irqdomainsexclusive") introduced an IRQ_DOMAIN_FLAG_NO_MAP flag to isolate the'nomap' domains still in use under the powerpc arch. With this newflag, the revmap_tree of the IRQ domain is not used anymore. Thischange broke the support of shared LSIs [1] in the XIVE driver becauseit was relying on a lookup in the revmap_tree to query previouslymapped interrupts. Linux now creates two distinct IRQ mappings on thesame HW IRQ which can lead to unexpected behavior in the drivers.The XIVE IRQ domain is not a direct mapping domain and its HW IRQinterrupt number space is rather large : 1M/socket on POWER9 andPOWER10, change the XIVE driver to use a 'tree' domain type instead.[1] For instance, a linux KVM guest with virtio-rng and virtio-balloon devices.Fixes: 4f86a06e2d6e ("irqdomain: Make normal and nomap irqdomains exclusive")Cc: stable@vger.kernel.org # v5.14+Signed-off-by: Cédric Le Goater Tested-by: Greg Kurz Acked-by: Marc Zyngier Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20211116134022.420412-1-clg@kaod.org List of files: /linux-6.15/arch/powerpc/sysdev/xive/Kconfig

e37af801 - powerpc: Move the use of irq_domain_add_nomap() behind a config option

Sun, 04 Apr 2021 12:06:39 +0000

powerpc: Move the use of irq_domain_add_nomap() behind a config optionOnly a handful of old PPC systems are still using the old 'nomap'variant of the irqdomain library. Move the associated definitionsbehind a configuration option, which will allow us to make somemore radical changes.Signed-off-by: Marc Zyngier List of files: /linux-6.15/arch/powerpc/sysdev/xive/Kconfig

719736e1 - powerpc: remove redundant 'default n' from Kconfig-s

Tue, 09 Oct 2018 15:39:46 +0000

powerpc: remove redundant 'default n' from Kconfig-s'default n' is the default value for any bool or tristate Kconfigsetting so there is no need to write it explicitly.Also since commit f467c5640c29 ("kconfig: only write '# CONFIG_FOOis not set' for visible symbols") the Kconfig behavior is the sameregardless of 'default n' being present or not: ... One side effect of (and the main motivation for) this change is making the following two definitions behave exactly the same: config FOO bool config FOO bool default n With this change, neither of these will generate a '# CONFIG_FOO is not set' line (assuming FOO isn't selected/implied). That might make it clearer to people that a bare 'default n' is redundant. ...Signed-off-by: Bartlomiej Zolnierkiewicz Signed-off-by: Michael Ellerman List of files: /linux-6.15/arch/powerpc/sysdev/xive/Kconfig

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/arch/powerpc/sysdev/xive/Kconfig

eac1e731 - powerpc/xive: guest exploitation of the XIVE interrupt controller

Wed, 30 Aug 2017 19:46:11 +0000

powerpc/xive: guest exploitation of the XIVE interrupt controllerThis is the framework for using XIVE in a PowerVM guest. The supportis very similar to the native one in a much simpler form.Each source is associated with an Event State Buffer (ESB). This is atwo bit state machine which is used to trigger events. The bits arenamed "P" (pending) and "Q" (queued) and can be controlled by MMIO.The Guest OS registers event (or notifications) queues on which the HWwill post event data for a target to notify.Instead of OPAL calls, a set of Hypervisors call are used to configurethe interrupt sources and the event/notification queues of the guest: - H_INT_GET_SOURCE_INFO used to obtain the address of the MMIO page of the Event State Buffer (PQ bits) entry associated with the source. - H_INT_SET_SOURCE_CONFIG assigns a source to a "target". - H_INT_GET_SOURCE_CONFIG determines to which "target" and "priority" is assigned to a source - H_INT_GET_QUEUE_INFO returns the address of the notification management page associated with the specified "target" and "priority". - H_INT_SET_QUEUE_CONFIG sets or resets the event queue for a given "target" and "priority". It is also used to set the notification config associated with the queue, only unconditional notification for the moment. Reset is performed with a queue size of 0 and queueing is disabled in that case. - H_INT_GET_QUEUE_CONFIG returns the queue settings for a given "target" and "priority". - H_INT_RESET resets all of the partition's interrupt exploitation structures to their initial state, losing all configuration set via the hcalls H_INT_SET_SOURCE_CONFIG and H_INT_SET_QUEUE_CONFIG. - H_INT_SYNC issue a synchronisation on a source to make sure sure all notifications have reached their queue.As for XICS, the XIVE interface for the guest is described in thedevice tree under the "interrupt-controller" node. A couple of newproperties are specific to XIVE : - "reg" contains the base address and size of the thread interrupt managnement areas (TIMA), also called rings, for the User level and for the Guest OS level. Only the Guest OS level is taken into account today. - "ibm,xive-eq-sizes" the size of the event queues. One cell per size supported, contains log2 of size, in ascending order. - "ibm,xive-lisn-ranges" the interrupt numbers ranges assigned to the guest. These are allocated using a simple bitmap.and also : - "/ibm,plat-res-int-priorities" contains a list of priorities that the hypervisor has reserved for its own use.Tested with a QEMU XIVE model for pseries and with the Power hypervisor.Signed-off-by: Cédric Le Goater Acked-by: Benjamin Herrenschmidt Signed-off-by: Michael Ellerman List of files: /linux-6.15/arch/powerpc/sysdev/xive/Kconfig

243e2511 - powerpc/xive: Native exploitation of the XIVE interrupt controller

Wed, 05 Apr 2017 07:54:50 +0000

powerpc/xive: Native exploitation of the XIVE interrupt controllerThe XIVE interrupt controller is the new interrupt controllerfound in POWER9. It supports advanced virtualization capabilitiesamong other things.Currently we use a set of firmware calls that simulate the old"XICS" interrupt controller but this is fairly inefficient.This adds the framework for using XIVE along with a nativebackend which OPAL for configuration. Later, a backend allowingthe use in a KVM or PowerVM guest will also be provided.This disables some fast path for interrupts in KVM when XIVE isenabled as these rely on the firmware emulation code which is nolonger available when the XIVE is used natively by Linux.A latter patch will make KVM also directly exploit the XIVE, thusrecovering the lost performance (and more).Signed-off-by: Benjamin Herrenschmidt [mpe: Fixup pr_xxx("XIVE:"...), don't split pr_xxx() strings, tweak Kconfig so XIVE_NATIVE selects XIVE and depends on POWERNV, fix build errors when SMP=n, fold in fixes from Ben: Don't call cpu_online() on an invalid CPU number Fix irq target selection returning out of bounds cpu# Extra sanity checks on cpu numbers ]Signed-off-by: Michael Ellerman List of files: /linux-6.15/arch/powerpc/sysdev/xive/Kconfig