cpufeatures merge candidate
Subsystems (3)
Nicholas Piggin
reviewerv2 cover cpufeatures merge candidate
I included binding documentation in OPAL, and wrote a design overview and implementation guideline document. Writing updated documentation lead to some small changes in the specification.
Also a number of other small changes to Linux and OPAL.
Thanks,
Nick
A message that is not in the archive (sent off-list or not yet received): 20170418191220.3166-1-npiggin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
PATCH 3/4 of/fdt: introduce of_scan_flat_dt_subnodes and of_get_flat_dt_phandle
Introduce primitives for FDT parsing. These will be used for powerpc cpufeatures node scanning, which has quite complex structure but should be processed early.
--- drivers/of/fdt.c | 38 ++++++++++++++++++++++++++++++++++++++ include/linux/of_fdt.h | 6 ++++++ 2 files changed, 44 insertions(+)
drivers/of/fdt.c +38 -0
@@ -754,6 +754,36 @@ int __init of_scan_flat_dt(int (*it)(unsigned long node, }/** +* of_scan_flat_dt_subnodes - scan sub-nodes of a node call callback on each. +* @it: callback function +* @data: context data pointer +* +* This function is used to scan sub-nodes of a node. +*/ +int __init of_scan_flat_dt_subnodes (unsigned long parent, +int (*it)(unsigned long node, +const char *uname, +void *data), +void *data) +{ +const void *blob = initial_boot_params; +int node; + +fdt_for_each_subnode (node, blob, parent) { +const char *pathp; +int rc; + + pathp =fdt_get_name (blob, node,NULL ); +if (*pathp =='/' ) + pathp =kbasename (pathp); + rc =it (node, pathp, data); +if (rc) +return rc; + } +return 0 ; +} + +/** * of_get_flat_dt_subnode_by_name - get the subnode by given name * * @node: the parent node
@@ -812,6 +842,14 @@ int __init of_flat_dt_match(unsigned long node, const char *const *compat)return of_fdt_match (initial_boot_params, node, compat); } +/** +* of_get_flat_dt_prop - Given a node in the flat blob, return the phandle +*/ +uint32_t __init of_get_flat_dt_phandle (unsigned long node) +{ +return fdt_get_phandle (initial_boot_params, node); +} +struct fdt_scan_status {const char *name;int namelen;
include/linux/of_fdt.h +6 -0
@@ -54,6 +54,11 @@ extern char __dtb_end[];extern int of_scan_flat_dt (int (*it)(unsigned long node,const char *uname,int depth,void *data),void *data); +extern int of_scan_flat_dt_subnodes (unsigned long node, +int (*it)(unsigned long node, +const char *uname, +void *data), +void *data);extern int of_get_flat_dt_subnode_by_name (unsigned long node,const char *uname); extern const void *of_get_flat_dt_prop(unsigned long node, const char *name,
@@ -62,6 +67,7 @@ extern int of_flat_dt_is_compatible(unsigned long node, const char *name);extern int of_flat_dt_match (unsigned long node,const char *const *matches);extern unsigned long of_get_flat_dt_root (void );extern int of_get_flat_dt_size (void ); +extern uint32_t of_get_flat_dt_phandle (unsigned long node);extern int early_init_dt_scan_chosen (unsigned long node,const char *uname,int depth,void *data);
Signature · 6 lines
2.11.0 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Nicholas Piggin
reviewerPATCH 1/1 cpu-features: add base and POWER8, POWER9 /cpus/ibm, powerpc-cpu-features dt
In reply to Nicholas PigginSince last time:
- Added binding specification and design overview documentation.
- Renamed the dt node to ibm,powerpc specific.
- Moved dependency building pass into its own function.
--- core/Makefile.inc | 2 +- core/cpufeatures.c | 896 +++++++++++++++++++++ core/device.c | 7 + core/init.c | 1 + .../ibm,powerpc-cpu-features/binding.txt | 226 ++++++ .../ibm,powerpc-cpu-features/design.txt | 157 ++++ include/device.h | 1 + include/skiboot.h | 5 + 8 files changed, 1294 insertions(+), 1 deletion(-) create mode 100644 core/cpufeatures.c create mode 100644 doc/device-tree/ibm,powerpc-cpu-features/binding.txt create mode 100644 doc/device-tree/ibm,powerpc-cpu-features/design.txt
core/Makefile.inc +1 -1
@@ -8,7 +8,7 @@ CORE_OBJS += pci-opal.o fast-reboot.o device.o exceptions.o trace.o affinity.o CORE_OBJS += vpd.o hostservices.o platform.o nvram.o nvram-format.o hmi.o CORE_OBJS += console-log.o ipmi.o time-utils.o pel.o pool.o errorlog.o CORE_OBJS += timer.o i2c.o rtc.o flash.o sensor.o ipmi-opal.o -CORE_OBJS += flash-subpartition.o bitmap.o buddy.o pci-quirk.o +CORE_OBJS += flash-subpartition.o bitmap.o buddy.o pci-quirk.o cpufeatures.o ifeq ($(SKIBOOT_GCOV),1) CORE_OBJS += gcov-profiling.o
core/cpufeatures.c new file +896 -0
896 lines not on this page · raw message
core/device.c +7 -0
@@ -598,6 +598,13 @@ u32 dt_property_get_cell(const struct dt_property *prop, u32 index)return fdt32_to_cpu (((const u32 *)prop->prop)[index]); } +void dt_property_set_cell (struct dt_property *prop,u32 index,u32 val) +{ +assert (prop->len >= (index+1 )*sizeof (u32)); +/* Always aligned, so this works. */ + ((u32 *)prop->prop)[index] =cpu_to_fdt32 (val); +} +/* First child of this node. */ struct dt_node *dt_first (const struct dt_node *root) {
core/init.c +1 -0
@@ -790,6 +790,7 @@ void __noreturn __nomcount main_cpu_entry(const void *fdt) }else {dt_expand (fdt); } +dt_add_cpufeatures (dt_root);/* Now that we have a full devicetree, verify that we aren't on fire. */ per_thread_sanity_checks ();
doc/device-tree/ibm,powerpc-cpu-features/binding.txt new file +226 -0
226 lines not on this page · raw message
doc/device-tree/ibm,powerpc-cpu-features/design.txt new file +157 -0
157 lines not on this page · raw message
include/device.h +1 -0
@@ -125,6 +125,7 @@ void dt_check_del_prop(struct dt_node *node, const char *name);/* Warning: moves *prop! */ void dt_resize_property (struct dt_property **prop,size_t len); +void dt_property_set_cell (struct dt_property *prop,u32 index,u32 val);u32 dt_property_get_cell (const struct dt_property *prop,u32 index);/* First child of this node. */
include/skiboot.h +5 -0
@@ -184,6 +184,11 @@ extern void start_kernel_secondary(uint64_t entry) __noreturn;/* Get description of machine from HDAT and create device-tree */ extern int parse_hdat (bool is_opal); +struct dt_node ; + +/* Add /cpus/features node for boot environment that passes an fdt */ +extern void dt_add_cpufeatures (struct dt_node *root); +/* Root of device tree. */ extern struct dt_node *dt_root;
Signature · 1 line
2.11.0
Nicholas Piggin
reviewerPATCH v2 1/4 powerpc/64s: Revert setting LPCR LPES0 on POWER9
In reply to Nicholas PigginThe XIVE enablement patches set LPES0 on POWER9 host. This bit sets external interrupts to guest delivery mode that uses SRR[01]. The host's EE interrupt handler expects HSRR[01] (for earlier CPUs). which is fine because XIVE is configured not to deliver EE to the host (HVI is used instead) so this should never be executed.
However a bug in interrupt controller code or odd configuration of mambo/systemsim could result in the host getting EE. Keeping EE delivery mode matching the host handler prevents strange crashes due to using the wrong exception registers.
When running in guest mode and getting EE, the guest LPCR will be loaded by KVM which contains the LPES0 bit.
--- arch/powerpc/kernel/cpu_setup_power.S | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
arch/powerpc/kernel/cpu_setup_power.S +2 -2
@@ -107,7 +107,7 @@ _GLOBAL(__setup_cpu_power9) or r3, r3, r4 LOAD_REG_IMMEDIATE(r4, LPCR_UPRT | LPCR_HR) andc r3, r3, r4 - li r4,(LPCR_LPES0 >> LPCR_LPES_SH) + li r4,0 /* LPES = 0 */ bl __init_LPCR bl __init_HFSCR bl __init_tlb_power9
@@ -131,7 +131,7 @@ _GLOBAL(__restore_cpu_power9) or r3, r3, r4 LOAD_REG_IMMEDIATE(r4, LPCR_UPRT | LPCR_HR) andc r3, r3, r4 - li r4,(LPCR_LPES0 >> LPCR_LPES_SH) + li r4,0 /* LPES = 0 */ bl __init_LPCR bl __init_HFSCR bl __init_tlb_power9
Signature · 1 line
2.11.0
Michael Ellerman
AppliedRe: [1/4] powerpc/64s: Revert setting LPCR LPES0 on POWER9
Quoted 11 lines · Nicholas Piggin
The XIVE enablement patches set LPES0 on POWER9 host. This bit sets external interrupts to guest delivery mode that uses SRR[01]. The host's EE interrupt handler expects HSRR[01] (for earlier CPUs). which is fine because XIVE is configured not to deliver EE to the host (HVI is used instead) so this should never be executed.
However a bug in interrupt controller code or odd configuration of mambo/systemsim could result in the host getting EE. Keeping EE delivery mode matching the host handler prevents strange crashes due to using the wrong exception registers.
Quoted 5 lines
When running in guest mode and getting EE, the guest LPCR will be loaded by KVM which contains the LPES0 bit.
Fixes 08a1e650cc ("powerpc: Fixup LPCR:PECE and HEIC setting on POWER9")Signed-off-by Nicholas Piggin <[email protected]>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/8d1b48ef580097e111c2644e6fc604
cheers
Nicholas Piggin
reviewerPATCH v2 2/4 powerpc/64s: POWER9 no LPCR VRMASD bits
In reply to Nicholas PigginPOWER9/ISAv3 has no VRMASD field in LPCR. Don't set reserved bits.
--- arch/powerpc/kernel/cpu_setup_power.S | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-)
arch/powerpc/kernel/cpu_setup_power.S +12 -9
@@ -30,7 +30,7 @@ _GLOBAL(__setup_cpu_power7) mtspr SPRN_LPID,r0 mfspr r3,SPRN_LPCR li r4,(LPCR_LPES1 >> LPCR_LPES_SH) - bl __init_LPCR + bl __init_LPCR_ISA206 bl __init_tlb_power7 mtlr r11 blr
@@ -44,7 +44,7 @@ _GLOBAL(__restore_cpu_power7) mtspr SPRN_LPID,r0 mfspr r3,SPRN_LPCR li r4,(LPCR_LPES1 >> LPCR_LPES_SH) - bl __init_LPCR + bl __init_LPCR_ISA206 bl __init_tlb_power7 mtlr r11 blr
@@ -62,7 +62,7 @@ _GLOBAL(__setup_cpu_power8) mfspr r3,SPRN_LPCR ori r3, r3, LPCR_PECEDH li r4,0 /* LPES = 0 */ - bl __init_LPCR + bl __init_LPCR_ISA206 bl __init_HFSCR bl __init_tlb_power8 bl __init_PMU_HV
@@ -84,7 +84,7 @@ _GLOBAL(__restore_cpu_power8) mfspr r3,SPRN_LPCR ori r3, r3, LPCR_PECEDH li r4,0 /* LPES = 0 */ - bl __init_LPCR + bl __init_LPCR_ISA206 bl __init_HFSCR bl __init_tlb_power8 bl __init_PMU_HV
@@ -108,7 +108,7 @@ _GLOBAL(__setup_cpu_power9) LOAD_REG_IMMEDIATE(r4, LPCR_UPRT | LPCR_HR) andc r3, r3, r4 li r4,0 /* LPES = 0 */ - bl __init_LPCR + bl __init_LPCR_ISA300 bl __init_HFSCR bl __init_tlb_power9 bl __init_PMU_HV
@@ -132,7 +132,7 @@ _GLOBAL(__restore_cpu_power9) LOAD_REG_IMMEDIATE(r4, LPCR_UPRT | LPCR_HR) andc r3, r3, r4 li r4,0 /* LPES = 0 */ - bl __init_LPCR + bl __init_LPCR_ISA300 bl __init_HFSCR bl __init_tlb_power9 bl __init_PMU_HV
@@ -150,7 +150,7 @@ __init_hvmode_206: std r5,CPU_SPEC_FEATURES(r4) blr -__init_LPCR: +__init_LPCR_ISA206: /* Setup a sane LPCR: * Called with initial LPCR in R3 and desired LPES 2-bit value in R4 *
@@ -163,6 +163,11 @@ __init_LPCR: * * Other bits untouched for now */ + li r5,0x10 + rldimi r3,r5, LPCR_VRMASD_SH, 64-LPCR_VRMASD_SH-5 + + /* POWER9 has no VRMASD */ +__init_LPCR_ISA300: rldimi r3,r4, LPCR_LPES_SH, 64-LPCR_LPES_SH-2 ori r3,r3,(LPCR_PECE0|LPCR_PECE1|LPCR_PECE2) li r5,4
@@ -170,8 +175,6 @@ __init_LPCR: clrrdi r3,r3,1 /* clear HDICE */ li r5,4 rldimi r3,r5, LPCR_VC_SH, 0 - li r5,0x10 - rldimi r3,r5, LPCR_VRMASD_SH, 64-LPCR_VRMASD_SH-5 mtspr SPRN_LPCR,r3 isync blr
Signature · 1 line
2.11.0
Michael Ellerman
AppliedRe: [2/4] powerpc/64s: POWER9 no LPCR VRMASD bits
Quoted 3 lines · Nicholas Piggin
POWER9/ISAv3 has no VRMASD field in LPCR. Don't set reserved bits.
Signed-off-by Nicholas Piggin <[email protected]>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/700b7eadd5625d22b8235fb21259b3
cheers
Nicholas Piggin
reviewerPATCH v2 4/4 powerpc/64s: cpu-features: initial implementation
In reply to Nicholas PigginThe /cpus/ibm,powerpc-cpu-features dt binding describes CPU features with ascii names and extensible compatibility, privilege, and enablement metadata that allows improved flexibility and compatibility with new hardware.
Design overview and specification of features is available in the OPAL source.
Since last post:
- Updated to powerpc next, in particular XIVE merge
- Updated and expanded documentation in skiboot. Device tree binding documentation in Linux is a copy of the binding specification from skiboot and includes a pointer back there.
- Renamed usable-mask to usable-privilege to describe it better
- Changed hv-support and os-support to bitmasks for better extensibility for other recipes in future.
Looking at hfscr/fscr/lpcr/msr etc bits before and after the patch to make sure we're doing things properly. There is one difference:
- PPC_FEATURE2_EBB is set independent of PMU init. EBB facility is theoretically more general than PMU, I don't think this should be a problem?
POWER9:
- CPU_FTR_ICSWX bit is now clear. Should this be cleared on POEWR9?
And Mambo has a few issues with POWER8:
- HFSCR bit 54 and 57 are now clear (mambo sets at init)
- PMAO_BUG is set. This is due to mambo setting architected POWER8 mode and POWER8E PVR. Current kernels lose PMAO_BUG bit.
- CI_LARGE_PAGE is now set (mambo boot does not set it for some reason, haven't looked at why).
--- .../bindings/powerpc/ibm,powerpc-cpu-features.txt | 233 ++++++++ arch/powerpc/Kconfig | 16 + arch/powerpc/include/asm/cpu_has_feature.h | 4 +- arch/powerpc/include/asm/cpufeatures.h | 55 ++ arch/powerpc/include/asm/cputable.h | 2 + arch/powerpc/include/uapi/asm/cputable.h | 6 + arch/powerpc/kernel/Makefile | 1 + arch/powerpc/kernel/cpufeatures.c | 636 +++++++++++++++++++++ arch/powerpc/kernel/cputable.c | 37 +- arch/powerpc/kernel/prom.c | 338 ++++++++++- arch/powerpc/kernel/setup-common.c | 2 +- arch/powerpc/kernel/setup_64.c | 15 +- 12 files changed, 1328 insertions(+), 17 deletions(-) create mode 100644 Documentation/devicetree/bindings/powerpc/ibm,powerpc-cpu-features.txt create mode 100644 arch/powerpc/include/asm/cpufeatures.h create mode 100644 arch/powerpc/kernel/cpufeatures.c
Documentation/devicetree/bindings/powerpc/ibm,powerpc-cpu-features.txt new file +233 -0
@@ -0,0 +1,233 @@ +*** NOTE *** +This document is copied from OPAL firmware +(skiboot/doc/device-tree/ibm,powerpc-cpu-features/binding.txt) + +There is more complete overview and documentation of features in that +source tree. All patches and modifications should go there. + +ibm,powerpc-cpu-features binding +================================ + +This device tree binding describes CPU features available to software, with +enablement, privilege, and compatibility metadata. + +More general description of design and implementation of this binding is +found in design.txt, which also points to documentation of specific features. + + +/cpus/ibm,powerpc-cpu-features node binding +------------------------------------------- + +Node: ibm,powerpc-cpu-features + +Description: Container of CPU feature nodes. + +The node name must be "ibm,powerpc-cpu-features" and it must be a child of the +node "/cpus". + +The node is optional but should be provided by new OPAL firmware. + +Properties: + +- device_type + Usage: required + Value type: string + Definition: "cpu-features" + +- isa + Usage: required + Value type: <u32> + Definition: + + isa that the CPU is currently running in. This provides instruction set + compatibility, less the individual feature nodes. For example, an ISA v3.0 + implementation that lacks the "transactional-memory" cpufeature node + should not use transactional memory facilities. + + Value corresponds to the "Power ISA Version" multiplied by 1000. + For example, <3000> corresponds to Version 3.0, <2070> to Version 2.07. + The minor digit is available for revisions. + +/cpus/ibm,powerpc-cpu-features/example-feature node bindings +---------------------------------------------------------------- + +Each child node of cpu-features represents a CPU feature / capability. + +Node: A string describing an architected CPU feature, e.g., "floating-point". + +Description: A feature or capability supported by the CPUs. + +The name of the node is a human readable string that forms the interface +used to describe features to software. Features are currently documented +in the code where they are implemented in skiboot/core/cpufeatures.c + +Presence of the node indicates the feature is available. + +Properties: + +- isa + Usage: required + Value type: <u32> + Definition: + + First level of the Power ISA that the feature appears in. + Software should filter out features when constraining the + environment to a particular ISA version. + + Value is defined similarly to /cpus/features/isa + +- usable-privilege + Usage: required + Value type: <u32> bit mask + Definition: + Bit numbers are LSB0 + bit 0 - PR (problem state / user mode) + bit 1 - OS (privileged state) + bit 2 - HV (hypervisor state) + All other bits reserved and should be zero. + + This property describes the privilege levels and/or software components + that can use the feature. + + If bit 0 is set, then the hwcap-bit-nr property will exist. + + +- hv-support + Usage: optional + Value type: <u32> bit mask + Definition: + Bit numbers are LSB0 + bit 0 - HFSCR + All other bits reserved and should be zero. + + This property describes the HV privilege support required to enable the + feature to lesser privilege levels. If the property does not exist then no + support is required. + + If no bits are set, the hypervisor must have explicit/custom support for + this feature. + + If the HFSCR bit is set, then the hfscr-bit-nr property will exist and + the feature may be enabled by setting this bit in the HFSCR register. + + +- os-support + Usage: optional + Value type: <u32> bit mask + Definition: + Bit numbers are LSB0 + bit 0 - FSCR + All other bits reserved and should be zero. + + This property describes the OS privilege support required to enable the + feature to lesser privilege levels. If the property does not exist then no + support is required. + + If no bits are set, the operating system must have explicit/custom support + for this feature. + + If the FSCR bit is set, then the fscr-bit-nr property will exist and + the feature may be enabled by setting this bit in the FSCR register. + + +- hfscr-bit-nr + Usage: optional + Value type: <u32> + Definition: HFSCR bit position (LSB0) + + This property exists when the hv-support property HFSCR bit is set. This + property describes the bit number in the HFSCR register that the + hypervisor must set in order to enable this feature. + + This property also exists if an HFSCR bit corresponds with this feature. + This makes CPU feature parsing slightly simpler. + + +- fscr-bit-nr + Usage: optional + Value type: <u32> + Definition: FSCR bit position (LSB0) + + This property exists when the os-support property FSCR bit is set. This + property describes the bit number in the FSCR register that the + operating system must set in order to enable this feature. + + This property also exists if an FSCR bit corresponds with this feature. + This makes CPU feature parsing slightly simpler. + + +- hwcap-bit-nr + Usage: optional + Value type: <u32> + Definition: Linux ELF AUX vector bit position (LSB0) + + This property may exist when the usable-privilege property value has PR bit set. + This property describes the bit number that should be set in the ELF AUX + hardware capability vectors in order to advertise this feature to userspace. + Bits 0-31 correspond to bits 0-31 in AT_HWCAP vector. Bits 32-63 correspond + to 0-31 in AT_HWCAP2 vector, and so on. Missing AT_HWCAPx vectors implies + that the feature is not enabled or can not be advertised. Operating systems + may provide a number of unassigned hardware capability bits to allow for new + features to be advertised. + + Some properties representing features created before this binding are + advertised to userspace without a one-to-one hwcap bit number may not specify + this bit. Operating system will handle those bits specifically. All new + features usable by userspace will have a hwcap-bit-nr property. + + +- dependencies + Usage: optional + Value type: <prop-encoded-array> + Definition: + + If this property exists then it is a list of phandles to cpu feature + nodes that must be enabled for this feature to be enabled. + + +Example +------- + + /cpus/ibm,powerpc-cpu-features { + device_type = "ibm,powerpc-cpu-features"; + + isa = <3020>; + + darn { + isa = <3000>; + usable-privilege = <1 | 2 | 4>; + hwcap-bit-nr = <xx>; + }; + + scv { + isa = <3000>; + usable-privilege = <1 | 2>; + os-support = <0>; + hwcap-bit-nr = <xx>; + }; + + stop { + isa = <3000>; + usable-privilege = <2 | 4>; + hv-support = <0>; + os-support = <0>; + }; + + vsx2 (hypothetical) { + isa = <3010>; + usable-privilege = <1 | 2 | 4>; + hv-support = <0>; + os-support = <0>; + hwcap-bit-nr = <xx>; + }; + + vsx2-newinsns { + isa = <3020>; + usable-privilege = <1 | 2 | 4>; + os-support = <1>; + fscr-bit-nr = <xx>; + hwcap-bit-nr = <xx>; + dependencies = <&vsx2>; + }; + + };
arch/powerpc/Kconfig +16 -0
@@ -330,6 +330,22 @@ source "arch/powerpc/platforms/Kconfig" menu "Kernel options" +config PPC_CPUFEATURES_DT + bool "cpufeatures cpu setup and device tree support (UNSTABLE)" + depends on PPC_BOOK3S_64 + default n + ---help--- + cpufeatures is a proposed new device tree binding for describing + CPU compatibility and features. Saying y here will attempt to use + cpufeatures binding if the firmware provides it. This binding is + not stable, so a kernel built with this option may not function + properly with future firmware. + +config PPC_CPUFEATURES_ENABLE_UNKNOWN + bool "cpufeatures pass through unknown features to guest/userspace" + depends on PPC_CPUFEATURES_DT + default y + config HIGHMEM bool "High memory support" depends on PPC32
arch/powerpc/include/asm/cpu_has_feature.h +2 -2
@@ -1,5 +1,5 @@ -#ifndef __ASM_POWERPC_CPUFEATURES_H -#define __ASM_POWERPC_CPUFEATURES_H +#ifndef __ASM_POWERPC_CPU_HAS_FEATURE_H +#define __ASM_POWERPC_CPU_HAS_FEATURE_H#ifndef __ASSEMBLY__
arch/powerpc/include/asm/cpufeatures.h new file +55 -0
55 lines not on this page · raw message
arch/powerpc/include/asm/cputable.h +2 -0
@@ -118,7 +118,9 @@ extern struct cpu_spec *cur_cpu_spec;extern unsigned int __start___ftr_fixup, __stop___ftr_fixup; +extern void set_cur_cpu_spec (struct cpu_spec *s);extern struct cpu_spec *identify_cpu (unsigned long offset,unsigned int pvr); +extern void identify_cpu_name (unsigned int pvr);extern void do_feature_fixups (unsigned long value,void *fixup_start,void *fixup_end);
arch/powerpc/include/uapi/asm/cputable.h +6 -0
@@ -1,6 +1,12 @@#ifndef _UAPI__ASM_POWERPC_CPUTABLE_H#define _UAPI__ASM_POWERPC_CPUTABLE_H +/* +* IMPORTANT! +* All future PPC_FEATURE_* definitions must be allocated by OPAL / skiboot +* firmware, in accordance with the ibm,powerpc-cpu-features specification. +*/ +/* in AT_HWCAP */ #define PPC_FEATURE_32 0x80000000#define PPC_FEATURE_64 0x40000000
arch/powerpc/kernel/Makefile +1 -0
@@ -58,6 +58,7 @@ obj-$(CONFIG_PPC_RTAS) += rtas.o rtas-rtc.o $(rtaspci-y-y) obj-$(CONFIG_PPC_RTAS_DAEMON) += rtasd.o obj-$(CONFIG_RTAS_FLASH) += rtas_flash.o obj-$(CONFIG_RTAS_PROC) += rtas-proc.o +obj-$(CONFIG_PPC_CPUFEATURES_DT) += cpufeatures.o obj-$(CONFIG_EEH) += eeh.o eeh_pe.o eeh_dev.o eeh_cache.o \ eeh_driver.o eeh_event.o eeh_sysfs.o obj-$(CONFIG_GENERIC_TBSYNC) += smp-tbsync.o
arch/powerpc/kernel/cpufeatures.c new file +636 -0
636 lines not on this page · raw message
arch/powerpc/kernel/cputable.c +35 -2
@@ -23,7 +23,9 @@#include <asm/mmu.h> #include <asm/setup.h> -struct cpu_spec * cur_cpu_spec =NULL ; +static struct cpu_spec the_cpu_spec__read_mostly ; + +struct cpu_spec * cur_cpu_spec__read_mostly =NULL ;EXPORT_SYMBOL (cur_cpu_spec);/* The platform string corresponding to the real PVR */
@@ -2179,7 +2181,15 @@ static struct cpu_spec __initdata cpu_specs[] = {#endif /* CONFIG_E500 */ }; -static struct cpu_spec the_cpu_spec; +void __init set_cur_cpu_spec (struct cpu_spec *s) +{ +struct cpu_spec *t = &the_cpu_spec; + + t =PTRRELOC (t); + *t = *s; + + *PTRRELOC (&cur_cpu_spec) = &the_cpu_spec; +}static struct cpu_spec *__init setup_cpu_spec (unsigned long offset,struct cpu_spec *s)
@@ -2266,6 +2276,29 @@ struct cpu_spec * __init identify_cpu(unsigned long offset, unsigned int pvr)return NULL ; } +/* +* Used by cpufeatures to get the name for CPUs with a PVR table. +* If they don't hae a PVR table, cpufeatures gets the name from +* cpu device-tree node. +*/ +void __init identify_cpu_name (unsigned int pvr) +{ +struct cpu_spec *s = cpu_specs; +struct cpu_spec *t = &the_cpu_spec; +int i; + + s =PTRRELOC (s); + t =PTRRELOC (t); + +for (i =0 ; i <ARRAY_SIZE (cpu_specs); i++,s++) { +if ((pvr & s->pvr_mask) == s->pvr_value) { + t->cpu_name = s->cpu_name; +return ; + } + } +} + +#ifdef CONFIG_JUMP_LABEL_FEATURE_CHECKS struct static_key_true cpu_feature_keys[NUM_CPU_FTR_KEYS ] = { [0 ... NUM_CPU_FTR_KEYS - 1] = STATIC_KEY_TRUE_INIT
arch/powerpc/kernel/prom.c +327 -11
374 lines not on this page · raw message
arch/powerpc/kernel/setup-common.c +1 -1
@@ -256,7 +256,7 @@ static int show_cpuinfo(struct seq_file *m, void *v)seq_printf (m,"processor\t: %lu\n" , cpu_id);seq_printf (m,"cpu\t\t: " ); -if (cur_cpu_spec->pvr_mask) +if (cur_cpu_spec->pvr_mask && cur_cpu_spec->cpu_name)seq_printf (m,"%s" , cur_cpu_spec->cpu_name);else seq_printf (m,"unknown (%08x)" , pvr);
arch/powerpc/kernel/setup_64.c +14 -1
@@ -49,6 +49,7 @@#include <asm/paca.h> #include <asm/time.h> #include <asm/cputable.h> +#include <asm/cpufeatures.h> #include <asm/sections.h> #include <asm/btext.h> #include <asm/nvram.h>
@@ -274,8 +275,17 @@ void __init early_setup(unsigned long dt_ptr)/* -------- printk is _NOT_ safe to use here ! ------- */ -/* Identify CPU type */ +#ifdef CONFIG_PPC_CPUFEATURES_DT +/* Setup flat device-tree pointer */ + initial_boot_params =__va (dt_ptr); +if (early_init_devtree_check_cpu_features_exists ()) +cpufeatures_setup_cpu (); +else +/* Legacy table-based approach when /cpus/features is missing */ +identify_cpu (0 ,mfspr (SPRN_PVR )); +#else identify_cpu (0 ,mfspr (SPRN_PVR )); +#endif /* Assume we're on cpu 0 for now. Don't write to the paca yet! */ initialise_paca (&boot_paca,0 );
@@ -541,6 +551,9 @@ void __init initialize_cache_info(void) dcache_bsize = ppc64_caches.l1d.block_size; icache_bsize = ppc64_caches.l1i.block_size; + cur_cpu_spec->dcache_bsize = dcache_bsize; + cur_cpu_spec->icache_bsize = icache_bsize; +DBG (" <- initialize_cache_info()\n" ); }
Signature · 1 line
2.11.0