ec8f24b7 - treewide: Add SPDX license identifier - Makefile/Kconfig

Sun, 19 May 2019 12:07:45 +0000

treewide: Add SPDX license identifier - Makefile/KconfigAdd SPDX license identifiers to all Make/Kconfig files which: - Have no license information of any formThese files fall under the project license, GPL v2 only. The resulting SPDXlicense identifier is: GPL-2.0-onlySigned-off-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/arch/x86/platform/intel-quark/Makefile

28a375df - x86/intel/quark: Add Isolated Memory Regions for Quark X1000

Fri, 30 Jan 2015 16:29:38 +0000

x86/intel/quark: Add Isolated Memory Regions for Quark X1000Intel's Quark X1000 SoC contains a set of registers calledIsolated Memory Regions. IMRs are accessed over the IOSF mailboxinterface. IMRs are areas carved out of memory that defineread/write access rights to the various system agents within theQuark system. For a given agent in the system it is possible tospecify if that agent may read or write an area of memorydefined by an IMR with a granularity of 1 KiB.Quark_SecureBootPRM_330234_001.pdf section 4.5 details theconcept of IMRs quark-x1000-datasheet.pdf section 12.7.4 detailsthe implementation of IMRs in silicon.eSRAM flush, CPU Snoop write-only, CPU SMM Mode, CPU non-SMMmode, RMU and PCIe Virtual Channels (VC0 and VC1) can haveindividual read/write access masks applied to them for a givenmemory region in Quark X1000. This enables IMRs to treat eachmemory transaction type listed above on an individual basis andto filter appropriately based on the IMR access mask for thememory region. Quark supports eight IMRs.Since all of the DMA capable SoC components in the X1000 aremapped to VC0 it is possible to define sections of memory asinvalid for DMA write operations originating from Ethernet, USB,SD and any other DMA capable south-cluster component on VC0.Similarly it is possible to mark kernel memory as non-SMM moderead/write only or to mark BIOS runtime memory as SMM modeaccessible only depending on the particular memory footprint ona given system.On an IMR violation Quark SoC X1000 systems are configured toreset the system, so ensuring that the IMR memory map isconsistent with the EFI provided memory map is critical toensure no IMR violations reset the system.The API for accessing IMRs is based on MTRR code but doesn'tprovide a /proc or /sys interface to manipulate IMRs. Definingthe size and extent of IMRs is exclusively the domain ofin-kernel code.Quark firmware sets up a series of locked IMRs around pieces ofmemory that firmware owns such as ACPI runtime data. During boota series of unlocked IMRs are placed around items in memory toguarantee no DMA modification of those items can take place.Grub also places an unlocked IMR around the kernel boot paramsdata structure and compressed kernel image. It is necessary forthe kernel to tear down all unlocked IMRs in order to ensurethat the kernel's view of memory passed via the EFI memory mapis consistent with the IMR memory map. Without tearing down allunlocked IMRs on boot transitory IMRs such as those used toprotect the compressed kernel image will cause IMR violations and system reboots.The IMR init code tears down all unlocked IMRs and sets aprotective IMR around the kernel .text and .rodata as onecontiguous block. This sanitizes the IMR memory map with respectto the EFI memory map and protects the read-only portions of thekernel from unwarranted DMA access.Tested-by: Ong, Boon Leong Signed-off-by: Bryan O'Donoghue Reviewed-by: Andy Shevchenko Reviewed-by: Darren Hart Reviewed-by: Ong, Boon Leong Cc: andy.shevchenko@gmail.comCc: dvhart@infradead.orgLink: http://lkml.kernel.org/r/1422635379-12476-2-git-send-email-pure.logic@nexus-software.ieSigned-off-by: Ingo Molnar List of files: /linux-6.15/arch/x86/platform/intel-quark/Makefile

Changes in Makefile

ec8f24b7 - treewide: Add SPDX license identifier - Makefile/Kconfig

28a375df - x86/intel/quark: Add Isolated Memory Regions for Quark X1000