2005-10-06 06:06:20 +04:00
/*
* Procedures for creating , accessing and interpreting the device tree .
*
* Paul Mackerras August 1996.
* Copyright ( C ) 1996 - 2005 Paul Mackerras .
*
* Adapted for 64 bit PowerPC by Dave Engebretsen and Peter Bergner .
* { engebret | bergner } @ us . ibm . com
*
* This program is free software ; you can redistribute it and / or
* modify it under the terms of the GNU General Public License
* as published by the Free Software Foundation ; either version
* 2 of the License , or ( at your option ) any later version .
*/
# undef DEBUG
# include <stdarg.h>
# include <linux/kernel.h>
# include <linux/string.h>
# include <linux/init.h>
# include <linux/threads.h>
# include <linux/spinlock.h>
# include <linux/types.h>
# include <linux/pci.h>
# include <linux/stringify.h>
# include <linux/delay.h>
# include <linux/initrd.h>
# include <linux/bitops.h>
2011-07-23 02:24:23 +04:00
# include <linux/export.h>
2005-12-04 10:39:48 +03:00
# include <linux/kexec.h>
2006-07-03 15:36:01 +04:00
# include <linux/irq.h>
2010-07-12 08:36:09 +04:00
# include <linux/memblock.h>
2012-10-02 20:57:57 +04:00
# include <linux/of.h>
2014-02-28 17:42:56 +04:00
# include <linux/of_fdt.h>
2014-04-01 00:15:00 +04:00
# include <linux/libfdt.h>
2016-01-06 03:45:51 +03:00
# include <linux/cpu.h>
2005-10-06 06:06:20 +04:00
# include <asm/prom.h>
# include <asm/rtas.h>
# include <asm/page.h>
# include <asm/processor.h>
# include <asm/irq.h>
# include <asm/io.h>
2005-12-04 10:39:37 +03:00
# include <asm/kdump.h>
2005-10-06 06:06:20 +04:00
# include <asm/smp.h>
# include <asm/mmu.h>
2010-01-28 16:23:22 +03:00
# include <asm/paca.h>
2005-10-06 06:06:20 +04:00
# include <asm/pgtable.h>
2017-10-12 13:17:18 +03:00
# include <asm/powernv.h>
2005-10-06 06:06:20 +04:00
# include <asm/iommu.h>
# include <asm/btext.h>
# include <asm/sections.h>
# include <asm/machdep.h>
2005-10-10 16:50:37 +04:00
# include <asm/pci-bridge.h>
2006-05-17 12:00:46 +04:00
# include <asm/kexec.h>
2011-09-19 21:44:57 +04:00
# include <asm/opal.h>
2012-02-16 05:14:22 +04:00
# include <asm/fadump.h>
2016-07-05 08:03:44 +03:00
# include <asm/epapr_hcalls.h>
2016-07-05 08:03:48 +03:00
# include <asm/firmware.h>
2017-05-09 06:16:52 +03:00
# include <asm/dt_cpu_ftrs.h>
2017-12-01 19:47:08 +03:00
# include <asm/drmem.h>
2011-09-19 21:44:57 +04:00
2008-04-21 22:22:34 +04:00
# include <mm/mmu_decl.h>
2005-10-06 06:06:20 +04:00
# ifdef DEBUG
# define DBG(fmt...) printk(KERN_ERR fmt)
# else
# define DBG(fmt...)
# endif
# ifdef CONFIG_PPC64
2006-04-13 06:52:33 +04:00
int __initdata iommu_is_off ;
2005-10-06 06:06:20 +04:00
int __initdata iommu_force_on ;
2005-10-31 05:07:02 +03:00
unsigned long tce_alloc_start , tce_alloc_end ;
2010-07-07 02:39:02 +04:00
u64 ppc64_rma_size ;
2005-10-06 06:06:20 +04:00
# endif
2011-05-12 00:58:18 +04:00
static phys_addr_t first_memblock_size ;
2011-05-25 22:09:12 +04:00
static int __initdata boot_cpu_count ;
2005-10-06 06:06:20 +04:00
2006-05-17 12:00:46 +04:00
static int __init early_parse_mem ( char * p )
{
if ( ! p )
return 1 ;
memory_limit = PAGE_ALIGN ( memparse ( p , & p ) ) ;
2012-08-21 05:42:33 +04:00
DBG ( " memory limit = 0x%llx \n " , memory_limit ) ;
2006-05-17 12:00:46 +04:00
return 0 ;
}
early_param ( " mem " , early_parse_mem ) ;
powerpc: Force page alignment for initrd reserved memory
When using 64K pages with a separate cpio rootfs, U-Boot will align
the rootfs on a 4K page boundary. When the memory is reserved, and
subsequent early memblock_alloc is called, it will allocate memory
between the 64K page alignment and reserved memory. When the reserved
memory is subsequently freed, it is done so by pages, causing the
early memblock_alloc requests to be re-used, which in my case, caused
the device-tree to be clobbered.
This patch forces the reserved memory for initrd to be kernel page
aligned, and will move the device tree if it overlaps with the range
extension of initrd. This patch will also consolidate the identical
function free_initrd_mem() from mm/init_32.c, init_64.c to mm/mem.c,
and adds the same range extension when freeing initrd. free_initrd_mem()
is also moved to the __init section.
Many thanks to Milton Miller for his input on this patch.
[BenH: Fixed build without CONFIG_BLK_DEV_INITRD]
Signed-off-by: Dave Carroll <dcarroll@astekcorp.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
2011-06-09 10:52:38 +04:00
/*
* overlaps_initrd - check for overlap with page aligned extension of
* initrd .
*/
static inline int overlaps_initrd ( unsigned long start , unsigned long size )
{
# ifdef CONFIG_BLK_DEV_INITRD
if ( ! initrd_start )
return 0 ;
return ( start + size ) > _ALIGN_DOWN ( initrd_start , PAGE_SIZE ) & &
start < = _ALIGN_UP ( initrd_end , PAGE_SIZE ) ;
# else
return 0 ;
# endif
}
2007-09-06 21:47:29 +04:00
/**
* move_device_tree - move tree to an unused area , if needed .
*
* The device tree may be allocated beyond our memory limit , or inside the
powerpc: Force page alignment for initrd reserved memory
When using 64K pages with a separate cpio rootfs, U-Boot will align
the rootfs on a 4K page boundary. When the memory is reserved, and
subsequent early memblock_alloc is called, it will allocate memory
between the 64K page alignment and reserved memory. When the reserved
memory is subsequently freed, it is done so by pages, causing the
early memblock_alloc requests to be re-used, which in my case, caused
the device-tree to be clobbered.
This patch forces the reserved memory for initrd to be kernel page
aligned, and will move the device tree if it overlaps with the range
extension of initrd. This patch will also consolidate the identical
function free_initrd_mem() from mm/init_32.c, init_64.c to mm/mem.c,
and adds the same range extension when freeing initrd. free_initrd_mem()
is also moved to the __init section.
Many thanks to Milton Miller for his input on this patch.
[BenH: Fixed build without CONFIG_BLK_DEV_INITRD]
Signed-off-by: Dave Carroll <dcarroll@astekcorp.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
2011-06-09 10:52:38 +04:00
* crash kernel region for kdump , or within the page aligned range of initrd .
* If so , move it out of the way .
2006-05-17 12:00:46 +04:00
*/
2008-03-28 19:07:45 +03:00
static void __init move_device_tree ( void )
2006-05-17 12:00:46 +04:00
{
unsigned long start , size ;
void * p ;
DBG ( " -> move_device_tree \n " ) ;
start = __pa ( initial_boot_params ) ;
2014-04-01 00:15:00 +04:00
size = fdt_totalsize ( initial_boot_params ) ;
2006-05-17 12:00:46 +04:00
2011-01-27 13:30:44 +03:00
if ( ( memory_limit & & ( start + size ) > PHYSICAL_START + memory_limit ) | |
powerpc: Force page alignment for initrd reserved memory
When using 64K pages with a separate cpio rootfs, U-Boot will align
the rootfs on a 4K page boundary. When the memory is reserved, and
subsequent early memblock_alloc is called, it will allocate memory
between the 64K page alignment and reserved memory. When the reserved
memory is subsequently freed, it is done so by pages, causing the
early memblock_alloc requests to be re-used, which in my case, caused
the device-tree to be clobbered.
This patch forces the reserved memory for initrd to be kernel page
aligned, and will move the device tree if it overlaps with the range
extension of initrd. This patch will also consolidate the identical
function free_initrd_mem() from mm/init_32.c, init_64.c to mm/mem.c,
and adds the same range extension when freeing initrd. free_initrd_mem()
is also moved to the __init section.
Many thanks to Milton Miller for his input on this patch.
[BenH: Fixed build without CONFIG_BLK_DEV_INITRD]
Signed-off-by: Dave Carroll <dcarroll@astekcorp.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
2011-06-09 10:52:38 +04:00
overlaps_crashkernel ( start , size ) | |
overlaps_initrd ( start , size ) ) {
2010-07-07 02:39:01 +04:00
p = __va ( memblock_alloc ( size , PAGE_SIZE ) ) ;
2006-05-17 12:00:46 +04:00
memcpy ( p , initial_boot_params , size ) ;
2014-04-01 00:15:00 +04:00
initial_boot_params = p ;
2006-05-17 12:00:46 +04:00
DBG ( " Moved device tree to 0x%p \n " , p ) ;
}
DBG ( " <- move_device_tree \n " ) ;
}
2005-10-06 06:06:20 +04:00
2006-05-03 17:04:37 +04:00
/*
* ibm , pa - features is a per - cpu property that contains a string of
* attribute descriptors , each of which has a 2 byte header plus up
* to 254 bytes worth of processor attribute bits . First header
* byte specifies the number of bytes following the header .
* Second header byte is an " attribute-specifier " type , of which
* zero is the only currently - defined value .
* Implementation : Pass in the byte and bit offset for the feature
* that we are interested in . The function will return - 1 if the
* pa - features property is missing , or a 1 / 0 to indicate if the feature
* is supported / not supported . Note that the bit numbers are
* big - endian to match the definition in PAPR .
*/
static struct ibm_pa_feature {
unsigned long cpu_features ; /* CPU_FTR_xxx bit */
2011-04-06 23:48:50 +04:00
unsigned long mmu_features ; /* MMU_FTR_xxx bit */
2006-05-03 17:04:37 +04:00
unsigned int cpu_user_ftrs ; /* PPC_FEATURE_xxx bit */
2016-04-15 05:07:24 +03:00
unsigned int cpu_user_ftrs2 ; /* PPC_FEATURE2_xxx bit */
2006-05-03 17:04:37 +04:00
unsigned char pabyte ; /* byte number in ibm,pa-features */
unsigned char pabit ; /* bit number (big-endian) */
unsigned char invert ; /* if 1, pa bit set => clear feature */
} ibm_pa_features [ ] __initdata = {
powerpc/64: Used named initialisers for ibm_pa_features
The ibm_pa_features array consists of structures that describe which bit
and byte in the ibm,pa-features property toggles one or more flags in
either the CPU, MMU, or user visible feature flags.
Each one consists of 7 values, which are all unsigned long, int or char,
meaning the compiler gives us no warning if we assign the wrong values
to the wrong elements. In fact we have had a bug here in the past, where
we were setting incorrect bits, see commit 6997e57d693b ("powerpc:
scan_features() updates incorrect bits for REAL_LE").
So switch to using named initialisers for the structure elements, to
reduce the likelihood of future bugs, and hopefully improve readability
also.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Reviewed-by: Balbir Singh <bsingharora@gmail.com>
2016-10-28 09:39:53 +03:00
{ . pabyte = 0 , . pabit = 0 , . cpu_user_ftrs = PPC_FEATURE_HAS_MMU } ,
{ . pabyte = 0 , . pabit = 1 , . cpu_user_ftrs = PPC_FEATURE_HAS_FPU } ,
{ . pabyte = 0 , . pabit = 3 , . cpu_features = CPU_FTR_CTRL } ,
{ . pabyte = 0 , . pabit = 6 , . cpu_features = CPU_FTR_NOEXECUTE } ,
{ . pabyte = 1 , . pabit = 2 , . mmu_features = MMU_FTR_CI_LARGE_PAGE } ,
2017-05-24 10:03:26 +03:00
# ifdef CONFIG_PPC_RADIX_MMU
powerpc/64: Used named initialisers for ibm_pa_features
The ibm_pa_features array consists of structures that describe which bit
and byte in the ibm,pa-features property toggles one or more flags in
either the CPU, MMU, or user visible feature flags.
Each one consists of 7 values, which are all unsigned long, int or char,
meaning the compiler gives us no warning if we assign the wrong values
to the wrong elements. In fact we have had a bug here in the past, where
we were setting incorrect bits, see commit 6997e57d693b ("powerpc:
scan_features() updates incorrect bits for REAL_LE").
So switch to using named initialisers for the structure elements, to
reduce the likelihood of future bugs, and hopefully improve readability
also.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Reviewed-by: Balbir Singh <bsingharora@gmail.com>
2016-10-28 09:39:53 +03:00
{ . pabyte = 40 , . pabit = 0 , . mmu_features = MMU_FTR_TYPE_RADIX } ,
2017-05-24 10:03:26 +03:00
# endif
powerpc/64: Used named initialisers for ibm_pa_features
The ibm_pa_features array consists of structures that describe which bit
and byte in the ibm,pa-features property toggles one or more flags in
either the CPU, MMU, or user visible feature flags.
Each one consists of 7 values, which are all unsigned long, int or char,
meaning the compiler gives us no warning if we assign the wrong values
to the wrong elements. In fact we have had a bug here in the past, where
we were setting incorrect bits, see commit 6997e57d693b ("powerpc:
scan_features() updates incorrect bits for REAL_LE").
So switch to using named initialisers for the structure elements, to
reduce the likelihood of future bugs, and hopefully improve readability
also.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Reviewed-by: Balbir Singh <bsingharora@gmail.com>
2016-10-28 09:39:53 +03:00
{ . pabyte = 1 , . pabit = 1 , . invert = 1 , . cpu_features = CPU_FTR_NODSISRALIGN } ,
{ . pabyte = 5 , . pabit = 0 , . cpu_features = CPU_FTR_REAL_LE ,
. cpu_user_ftrs = PPC_FEATURE_TRUE_LE } ,
2014-11-02 17:32:42 +03:00
/*
2016-04-15 05:08:19 +03:00
* If the kernel doesn ' t support TM ( ie CONFIG_PPC_TRANSACTIONAL_MEM = n ) ,
* we don ' t want to turn on TM here , so we use the * _COMP versions
* which are 0 if the kernel doesn ' t support TM .
2014-11-02 17:32:42 +03:00
*/
powerpc/64: Used named initialisers for ibm_pa_features
The ibm_pa_features array consists of structures that describe which bit
and byte in the ibm,pa-features property toggles one or more flags in
either the CPU, MMU, or user visible feature flags.
Each one consists of 7 values, which are all unsigned long, int or char,
meaning the compiler gives us no warning if we assign the wrong values
to the wrong elements. In fact we have had a bug here in the past, where
we were setting incorrect bits, see commit 6997e57d693b ("powerpc:
scan_features() updates incorrect bits for REAL_LE").
So switch to using named initialisers for the structure elements, to
reduce the likelihood of future bugs, and hopefully improve readability
also.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Reviewed-by: Balbir Singh <bsingharora@gmail.com>
2016-10-28 09:39:53 +03:00
{ . pabyte = 22 , . pabit = 0 , . cpu_features = CPU_FTR_TM_COMP ,
. cpu_user_ftrs2 = PPC_FEATURE2_HTM_COMP | PPC_FEATURE2_HTM_NOSC_COMP } ,
2006-05-03 17:04:37 +04:00
} ;
2014-04-02 08:49:03 +04:00
static void __init scan_features ( unsigned long node , const unsigned char * ftrs ,
2006-11-10 12:38:53 +03:00
unsigned long tablelen ,
struct ibm_pa_feature * fp ,
unsigned long ft_size )
2006-05-03 17:04:37 +04:00
{
2006-11-10 12:38:53 +03:00
unsigned long i , len , bit ;
2006-05-03 17:04:37 +04:00
/* find descriptor with type == 0 */
for ( ; ; ) {
if ( tablelen < 3 )
return ;
2006-11-10 12:38:53 +03:00
len = 2 + ftrs [ 0 ] ;
2006-05-03 17:04:37 +04:00
if ( tablelen < len )
return ; /* descriptor 0 not found */
2006-11-10 12:38:53 +03:00
if ( ftrs [ 1 ] = = 0 )
2006-05-03 17:04:37 +04:00
break ;
tablelen - = len ;
2006-11-10 12:38:53 +03:00
ftrs + = len ;
2006-05-03 17:04:37 +04:00
}
/* loop over bits we know about */
2006-11-10 12:38:53 +03:00
for ( i = 0 ; i < ft_size ; + + i , + + fp ) {
if ( fp - > pabyte > = ftrs [ 0 ] )
2006-05-03 17:04:37 +04:00
continue ;
2006-11-10 12:38:53 +03:00
bit = ( ftrs [ 2 + fp - > pabyte ] > > ( 7 - fp - > pabit ) ) & 1 ;
2006-05-03 17:04:37 +04:00
if ( bit ^ fp - > invert ) {
cur_cpu_spec - > cpu_features | = fp - > cpu_features ;
cur_cpu_spec - > cpu_user_features | = fp - > cpu_user_ftrs ;
2016-04-15 05:07:24 +03:00
cur_cpu_spec - > cpu_user_features2 | = fp - > cpu_user_ftrs2 ;
2011-04-06 23:48:50 +04:00
cur_cpu_spec - > mmu_features | = fp - > mmu_features ;
2006-05-03 17:04:37 +04:00
} else {
cur_cpu_spec - > cpu_features & = ~ fp - > cpu_features ;
cur_cpu_spec - > cpu_user_features & = ~ fp - > cpu_user_ftrs ;
2016-04-15 05:07:24 +03:00
cur_cpu_spec - > cpu_user_features2 & = ~ fp - > cpu_user_ftrs2 ;
2011-04-06 23:48:50 +04:00
cur_cpu_spec - > mmu_features & = ~ fp - > mmu_features ;
2006-05-03 17:04:37 +04:00
}
}
}
2006-11-10 12:38:53 +03:00
static void __init check_cpu_pa_features ( unsigned long node )
{
2014-04-02 08:49:03 +04:00
const unsigned char * pa_ftrs ;
int tablelen ;
2006-11-10 12:38:53 +03:00
pa_ftrs = of_get_flat_dt_prop ( node , " ibm,pa-features " , & tablelen ) ;
if ( pa_ftrs = = NULL )
return ;
scan_features ( node , pa_ftrs , tablelen ,
ibm_pa_features , ARRAY_SIZE ( ibm_pa_features ) ) ;
}
2017-10-19 07:08:43 +03:00
# ifdef CONFIG_PPC_BOOK3S_64
2015-07-29 10:10:03 +03:00
static void __init init_mmu_slb_size ( unsigned long node )
2007-12-06 09:24:48 +03:00
{
2014-04-02 08:49:03 +04:00
const __be32 * slb_size_ptr ;
2007-12-06 09:24:48 +03:00
2015-07-29 10:10:03 +03:00
slb_size_ptr = of_get_flat_dt_prop ( node , " slb-size " , NULL ) ? :
of_get_flat_dt_prop ( node , " ibm,slb-size " , NULL ) ;
if ( slb_size_ptr )
2013-08-06 20:01:27 +04:00
mmu_slb_size = be32_to_cpup ( slb_size_ptr ) ;
2007-12-06 09:24:48 +03:00
}
# else
2015-07-29 10:10:03 +03:00
# define init_mmu_slb_size(node) do { } while(0)
2007-12-06 09:24:48 +03:00
# endif
2006-11-10 12:38:53 +03:00
static struct feature_property {
const char * name ;
u32 min_value ;
unsigned long cpu_feature ;
unsigned long cpu_user_ftr ;
} feature_properties [ ] __initdata = {
# ifdef CONFIG_ALTIVEC
{ " altivec " , 0 , CPU_FTR_ALTIVEC , PPC_FEATURE_HAS_ALTIVEC } ,
{ " ibm,vmx " , 1 , CPU_FTR_ALTIVEC , PPC_FEATURE_HAS_ALTIVEC } ,
# endif /* CONFIG_ALTIVEC */
2008-06-25 08:07:18 +04:00
# ifdef CONFIG_VSX
/* Yes, this _really_ is ibm,vmx == 2 to enable VSX */
{ " ibm,vmx " , 2 , CPU_FTR_VSX , PPC_FEATURE_HAS_VSX } ,
# endif /* CONFIG_VSX */
2006-11-10 12:38:53 +03:00
# ifdef CONFIG_PPC64
{ " ibm,dfp " , 1 , 0 , PPC_FEATURE_HAS_DFP } ,
{ " ibm,purr " , 1 , CPU_FTR_PURR , 0 } ,
{ " ibm,spurr " , 1 , CPU_FTR_SPURR , 0 } ,
# endif /* CONFIG_PPC64 */
} ;
2007-12-21 19:24:02 +03:00
# if defined(CONFIG_44x) && defined(CONFIG_PPC_FPU)
static inline void identical_pvr_fixup ( unsigned long node )
{
unsigned int pvr ;
2014-04-02 08:49:03 +04:00
const char * model = of_get_flat_dt_prop ( node , " model " , NULL ) ;
2007-12-21 19:24:02 +03:00
/*
* Since 440 GR ( x ) / 440 EP ( x ) processors have the same pvr ,
* we check the node path and set bit 28 in the cur_cpu_spec
* pvr for EP ( x ) processor version . This bit is always 0 in
* the " real " pvr . Then we call identify_cpu again with
* the new logical pvr to enable FPU support .
*/
if ( model & & strstr ( model , " 440EP " ) ) {
pvr = cur_cpu_spec - > pvr_value | 0x8 ;
identify_cpu ( 0 , pvr ) ;
DBG ( " Using logical pvr %x for %s \n " , pvr , model ) ;
}
}
# else
# define identical_pvr_fixup(node) do { } while(0)
# endif
2006-11-10 12:38:53 +03:00
static void __init check_cpu_feature_properties ( unsigned long node )
{
2018-03-02 22:49:18 +03:00
int i ;
2006-11-10 12:38:53 +03:00
struct feature_property * fp = feature_properties ;
2013-08-06 20:01:27 +04:00
const __be32 * prop ;
2006-11-10 12:38:53 +03:00
2018-03-02 22:49:18 +03:00
for ( i = 0 ; i < ( int ) ARRAY_SIZE ( feature_properties ) ; + + i , + + fp ) {
2006-11-10 12:38:53 +03:00
prop = of_get_flat_dt_prop ( node , fp - > name , NULL ) ;
2013-08-06 20:01:27 +04:00
if ( prop & & be32_to_cpup ( prop ) > = fp - > min_value ) {
2006-11-10 12:38:53 +03:00
cur_cpu_spec - > cpu_features | = fp - > cpu_feature ;
cur_cpu_spec - > cpu_user_features | = fp - > cpu_user_ftr ;
}
}
}
2005-10-06 06:06:20 +04:00
static int __init early_init_dt_scan_cpus ( unsigned long node ,
2006-03-25 09:25:17 +03:00
const char * uname , int depth ,
void * data )
2005-10-06 06:06:20 +04:00
{
2014-04-02 08:49:03 +04:00
const char * type = of_get_flat_dt_prop ( node , " device_type " , NULL ) ;
2013-08-06 20:01:27 +04:00
const __be32 * prop ;
const __be32 * intserv ;
2006-03-25 09:25:17 +03:00
int i , nthreads ;
2014-04-02 08:49:03 +04:00
int len ;
2011-03-16 06:54:35 +03:00
int found = - 1 ;
2011-05-20 11:50:18 +04:00
int found_thread = 0 ;
2005-10-06 06:06:20 +04:00
/* We are scanning "cpu" nodes only */
if ( type = = NULL | | strcmp ( type , " cpu " ) ! = 0 )
return 0 ;
2006-03-25 09:25:17 +03:00
/* Get physical cpuid */
intserv = of_get_flat_dt_prop ( node , " ibm,ppc-interrupt-server#s " , & len ) ;
2011-12-08 11:20:27 +04:00
if ( ! intserv )
intserv = of_get_flat_dt_prop ( node , " reg " , & len ) ;
nthreads = len / sizeof ( int ) ;
2006-03-25 09:25:17 +03:00
/*
* Now see if any of these threads match our boot cpu .
* NOTE : This must match the parsing done in smp_setup_cpu_maps .
*/
for ( i = 0 ; i < nthreads ; i + + ) {
2018-05-09 16:42:27 +03:00
if ( be32_to_cpu ( intserv [ i ] ) = =
fdt_boot_cpuid_phys ( initial_boot_params ) ) {
found = boot_cpu_count ;
found_thread = i ;
2005-10-06 06:06:20 +04:00
}
2006-03-25 09:25:17 +03:00
# ifdef CONFIG_SMP
/* logical cpu id is always 0 on UP kernels */
2011-03-16 06:54:35 +03:00
boot_cpu_count + + ;
2006-03-25 09:25:17 +03:00
# endif
}
2014-03-28 06:36:28 +04:00
/* Not the boot CPU */
if ( found < 0 )
return 0 ;
2005-10-06 06:06:20 +04:00
2014-03-28 06:36:28 +04:00
DBG ( " boot cpu: logical %d physical %d \n " , found ,
be32_to_cpu ( intserv [ found_thread ] ) ) ;
boot_cpuid = found ;
2007-12-21 19:24:02 +03:00
2014-03-28 06:36:28 +04:00
/*
* PAPR defines " logical " PVR values for cpus that
* meet various levels of the architecture :
* 0x0f000001 Architecture version 2.04
* 0x0f000002 Architecture version 2.05
* If the cpu - version property in the cpu node contains
* such a value , we call identify_cpu again with the
* logical PVR value in order to use the cpu feature
* bits appropriate for the architecture level .
*
* A POWER6 partition in " POWER6 architected " mode
* uses the 0x0f000002 PVR value ; in POWER5 + mode
* it uses 0x0f000001 .
2017-05-09 06:16:52 +03:00
*
* If we ' re using device tree CPU feature discovery then we don ' t
* support the cpu - version property , and it ' s the responsibility of the
* firmware / hypervisor to provide the correct feature set for the
* architecture level via the ibm , powerpc - cpu - features binding .
2014-03-28 06:36:28 +04:00
*/
2017-05-09 06:16:52 +03:00
if ( ! dt_cpu_ftrs_in_use ( ) ) {
prop = of_get_flat_dt_prop ( node , " cpu-version " , NULL ) ;
if ( prop & & ( be32_to_cpup ( prop ) & 0xff000000 ) = = 0x0f000000 )
identify_cpu ( 0 , be32_to_cpup ( prop ) ) ;
2014-03-28 06:36:28 +04:00
2017-05-09 06:16:52 +03:00
check_cpu_feature_properties ( node ) ;
check_cpu_pa_features ( node ) ;
}
2005-10-06 06:06:20 +04:00
2017-05-09 06:16:52 +03:00
identical_pvr_fixup ( node ) ;
2015-07-29 10:10:03 +03:00
init_mmu_slb_size ( node ) ;
2006-05-03 17:04:37 +04:00
2014-03-28 06:36:26 +04:00
# ifdef CONFIG_PPC64
2017-05-09 06:16:52 +03:00
if ( nthreads = = 1 )
2006-03-25 09:25:17 +03:00
cur_cpu_spec - > cpu_features & = ~ CPU_FTR_SMT ;
2017-05-09 06:16:52 +03:00
else if ( ! dt_cpu_ftrs_in_use ( ) )
cur_cpu_spec - > cpu_features | = CPU_FTR_SMT ;
2018-02-13 18:08:19 +03:00
allocate_paca ( boot_cpuid ) ;
2005-10-06 06:06:20 +04:00
# endif
2018-02-13 18:08:19 +03:00
set_hard_smp_processor_id ( found , be32_to_cpu ( intserv [ found_thread ] ) ) ;
2017-05-09 06:16:52 +03:00
2005-10-06 06:06:20 +04:00
return 0 ;
}
2014-08-20 02:55:18 +04:00
static int __init early_init_dt_scan_chosen_ppc ( unsigned long node ,
const char * uname ,
int depth , void * data )
2005-10-06 06:06:20 +04:00
{
2014-04-02 08:49:03 +04:00
const unsigned long * lprop ; /* All these set by kernel, so no need to convert endian */
2005-10-06 06:06:20 +04:00
2010-10-20 21:45:14 +04:00
/* Use common scan routine to determine if this is the chosen node */
if ( early_init_dt_scan_chosen ( node , uname , depth , data ) = = 0 )
return 0 ;
2005-10-06 06:06:20 +04:00
# ifdef CONFIG_PPC64
/* check if iommu is forced on or off */
2005-11-07 03:06:55 +03:00
if ( of_get_flat_dt_prop ( node , " linux,iommu-off " , NULL ) ! = NULL )
2005-10-06 06:06:20 +04:00
iommu_is_off = 1 ;
2005-11-07 03:06:55 +03:00
if ( of_get_flat_dt_prop ( node , " linux,iommu-force-on " , NULL ) ! = NULL )
2005-10-06 06:06:20 +04:00
iommu_force_on = 1 ;
# endif
2006-05-17 12:00:46 +04:00
/* mem=x on the command line is the preferred mechanism */
2009-12-11 09:42:21 +03:00
lprop = of_get_flat_dt_prop ( node , " linux,memory-limit " , NULL ) ;
if ( lprop )
memory_limit = * lprop ;
2005-10-06 06:06:20 +04:00
# ifdef CONFIG_PPC64
2009-12-11 09:42:21 +03:00
lprop = of_get_flat_dt_prop ( node , " linux,tce-alloc-start " , NULL ) ;
if ( lprop )
tce_alloc_start = * lprop ;
lprop = of_get_flat_dt_prop ( node , " linux,tce-alloc-end " , NULL ) ;
if ( lprop )
tce_alloc_end = * lprop ;
2005-10-06 06:06:20 +04:00
# endif
2016-11-29 15:45:50 +03:00
# ifdef CONFIG_KEXEC_CORE
2009-01-06 16:54:25 +03:00
lprop = of_get_flat_dt_prop ( node , " linux,crashkernel-base " , NULL ) ;
2007-09-06 21:46:15 +04:00
if ( lprop )
crashk_res . start = * lprop ;
2005-12-04 10:39:48 +03:00
2009-01-06 16:54:25 +03:00
lprop = of_get_flat_dt_prop ( node , " linux,crashkernel-size " , NULL ) ;
2007-09-06 21:46:15 +04:00
if ( lprop )
crashk_res . end = crashk_res . start + * lprop - 1 ;
2005-12-04 10:39:48 +03:00
# endif
2010-10-20 21:45:14 +04:00
/* break now */
return 1 ;
2005-10-06 06:06:20 +04:00
}
[POWERPC] Support ibm,dynamic-reconfiguration-memory nodes
For PAPR partitions with large amounts of memory, the firmware has an
alternative, more compact representation for the information about the
memory in the partition and its NUMA associativity information. This
adds the code to the kernel to parse this alternative representation.
The other part of this patch is telling the firmware that we can
handle the alternative representation. There is however a subtlety
here, because the firmware will invoke a reboot if the memory
representation we request is different from the representation that
firmware is currently using. This is because firmware can't change
the representation on the fly. Further, some firmware versions used
on POWER5+ machines have a bug where this reboot leaves the machine
with an altered value of load-base, which will prevent any kernel
booting until it is reset to the normal value (0x4000). Because of
this bug, we do NOT set fake_elf.rpanote.new_mem_def = 1, and thus we
do not request the new representation on POWER5+ and earlier machines.
We do request the new representation on POWER6, which uses the
ibm,client-architecture-support call.
Signed-off-by: Paul Mackerras <paulus@samba.org>
2006-11-29 14:27:42 +03:00
# ifdef CONFIG_PPC_PSERIES
/*
2017-12-01 19:47:08 +03:00
* Interpret the ibm dynamic reconfiguration memory LMBs .
[POWERPC] Support ibm,dynamic-reconfiguration-memory nodes
For PAPR partitions with large amounts of memory, the firmware has an
alternative, more compact representation for the information about the
memory in the partition and its NUMA associativity information. This
adds the code to the kernel to parse this alternative representation.
The other part of this patch is telling the firmware that we can
handle the alternative representation. There is however a subtlety
here, because the firmware will invoke a reboot if the memory
representation we request is different from the representation that
firmware is currently using. This is because firmware can't change
the representation on the fly. Further, some firmware versions used
on POWER5+ machines have a bug where this reboot leaves the machine
with an altered value of load-base, which will prevent any kernel
booting until it is reset to the normal value (0x4000). Because of
this bug, we do NOT set fake_elf.rpanote.new_mem_def = 1, and thus we
do not request the new representation on POWER5+ and earlier machines.
We do request the new representation on POWER6, which uses the
ibm,client-architecture-support call.
Signed-off-by: Paul Mackerras <paulus@samba.org>
2006-11-29 14:27:42 +03:00
* This contains a list of memory blocks along with NUMA affinity
* information .
*/
2017-12-01 19:47:08 +03:00
static void __init early_init_drmem_lmb ( struct drmem_lmb * lmb ,
const __be32 * * usm )
[POWERPC] Support ibm,dynamic-reconfiguration-memory nodes
For PAPR partitions with large amounts of memory, the firmware has an
alternative, more compact representation for the information about the
memory in the partition and its NUMA associativity information. This
adds the code to the kernel to parse this alternative representation.
The other part of this patch is telling the firmware that we can
handle the alternative representation. There is however a subtlety
here, because the firmware will invoke a reboot if the memory
representation we request is different from the representation that
firmware is currently using. This is because firmware can't change
the representation on the fly. Further, some firmware versions used
on POWER5+ machines have a bug where this reboot leaves the machine
with an altered value of load-base, which will prevent any kernel
booting until it is reset to the normal value (0x4000). Because of
this bug, we do NOT set fake_elf.rpanote.new_mem_def = 1, and thus we
do not request the new representation on POWER5+ and earlier machines.
We do request the new representation on POWER6, which uses the
ibm,client-architecture-support call.
Signed-off-by: Paul Mackerras <paulus@samba.org>
2006-11-29 14:27:42 +03:00
{
2017-12-01 19:47:08 +03:00
u64 base , size ;
int is_kexec_kdump = 0 , rngs ;
[POWERPC] Support ibm,dynamic-reconfiguration-memory nodes
For PAPR partitions with large amounts of memory, the firmware has an
alternative, more compact representation for the information about the
memory in the partition and its NUMA associativity information. This
adds the code to the kernel to parse this alternative representation.
The other part of this patch is telling the firmware that we can
handle the alternative representation. There is however a subtlety
here, because the firmware will invoke a reboot if the memory
representation we request is different from the representation that
firmware is currently using. This is because firmware can't change
the representation on the fly. Further, some firmware versions used
on POWER5+ machines have a bug where this reboot leaves the machine
with an altered value of load-base, which will prevent any kernel
booting until it is reset to the normal value (0x4000). Because of
this bug, we do NOT set fake_elf.rpanote.new_mem_def = 1, and thus we
do not request the new representation on POWER5+ and earlier machines.
We do request the new representation on POWER6, which uses the
ibm,client-architecture-support call.
Signed-off-by: Paul Mackerras <paulus@samba.org>
2006-11-29 14:27:42 +03:00
2017-12-01 19:47:08 +03:00
base = lmb - > base_addr ;
size = drmem_lmb_size ( ) ;
rngs = 1 ;
[POWERPC] Support ibm,dynamic-reconfiguration-memory nodes
For PAPR partitions with large amounts of memory, the firmware has an
alternative, more compact representation for the information about the
memory in the partition and its NUMA associativity information. This
adds the code to the kernel to parse this alternative representation.
The other part of this patch is telling the firmware that we can
handle the alternative representation. There is however a subtlety
here, because the firmware will invoke a reboot if the memory
representation we request is different from the representation that
firmware is currently using. This is because firmware can't change
the representation on the fly. Further, some firmware versions used
on POWER5+ machines have a bug where this reboot leaves the machine
with an altered value of load-base, which will prevent any kernel
booting until it is reset to the normal value (0x4000). Because of
this bug, we do NOT set fake_elf.rpanote.new_mem_def = 1, and thus we
do not request the new representation on POWER5+ and earlier machines.
We do request the new representation on POWER6, which uses the
ibm,client-architecture-support call.
Signed-off-by: Paul Mackerras <paulus@samba.org>
2006-11-29 14:27:42 +03:00
2017-12-01 19:47:08 +03:00
/*
* Skip this block if the reserved bit is set in flags
* or if the block is not assigned to this partition .
*/
if ( ( lmb - > flags & DRCONF_MEM_RESERVED ) | |
! ( lmb - > flags & DRCONF_MEM_ASSIGNED ) )
return ;
[POWERPC] Support ibm,dynamic-reconfiguration-memory nodes
For PAPR partitions with large amounts of memory, the firmware has an
alternative, more compact representation for the information about the
memory in the partition and its NUMA associativity information. This
adds the code to the kernel to parse this alternative representation.
The other part of this patch is telling the firmware that we can
handle the alternative representation. There is however a subtlety
here, because the firmware will invoke a reboot if the memory
representation we request is different from the representation that
firmware is currently using. This is because firmware can't change
the representation on the fly. Further, some firmware versions used
on POWER5+ machines have a bug where this reboot leaves the machine
with an altered value of load-base, which will prevent any kernel
booting until it is reset to the normal value (0x4000). Because of
this bug, we do NOT set fake_elf.rpanote.new_mem_def = 1, and thus we
do not request the new representation on POWER5+ and earlier machines.
We do request the new representation on POWER6, which uses the
ibm,client-architecture-support call.
Signed-off-by: Paul Mackerras <paulus@samba.org>
2006-11-29 14:27:42 +03:00
2017-12-01 19:47:08 +03:00
if ( * usm )
powerpc: Add support for dynamic reconfiguration memory in kexec/kdump kernels
Kdump kernel needs to use only those memory regions that it is allowed
to use (crashkernel, rtas, tce, etc.). Each of these regions have
their own sizes and are currently added under 'linux,usable-memory'
property under each memory@xxx node of the device tree.
The ibm,dynamic-memory property of ibm,dynamic-reconfiguration-memory
node (on POWER6) now stores in it the representation for most of the
logical memory blocks with the size of each memory block being a
constant (lmb_size). If one or more or part of the above mentioned
regions lie under one of the lmb from ibm,dynamic-memory property,
there is a need to identify those regions within the given lmb.
This makes the kernel recognize a new 'linux,drconf-usable-memory'
property added by kexec-tools. Each entry in this property is of the
form of a count followed by that many (base, size) pairs for the above
mentioned regions. The number of cells in the count value is given by
the #size-cells property of the root node.
Signed-off-by: Chandru Siddalingappa <chandru@in.ibm.com>
Signed-off-by: Paul Mackerras <paulus@samba.org>
2008-08-29 18:28:16 +04:00
is_kexec_kdump = 1 ;
2017-12-01 19:47:08 +03:00
if ( is_kexec_kdump ) {
/*
* For each memblock in ibm , dynamic - memory , a
* corresponding entry in linux , drconf - usable - memory
* property contains a counter ' p ' followed by ' p '
* ( base , size ) duple . Now read the counter from
* linux , drconf - usable - memory property
*/
rngs = dt_mem_next_cell ( dt_root_size_cells , usm ) ;
if ( ! rngs ) /* there are no (base, size) duple */
return ;
}
do {
powerpc: Add support for dynamic reconfiguration memory in kexec/kdump kernels
Kdump kernel needs to use only those memory regions that it is allowed
to use (crashkernel, rtas, tce, etc.). Each of these regions have
their own sizes and are currently added under 'linux,usable-memory'
property under each memory@xxx node of the device tree.
The ibm,dynamic-memory property of ibm,dynamic-reconfiguration-memory
node (on POWER6) now stores in it the representation for most of the
logical memory blocks with the size of each memory block being a
constant (lmb_size). If one or more or part of the above mentioned
regions lie under one of the lmb from ibm,dynamic-memory property,
there is a need to identify those regions within the given lmb.
This makes the kernel recognize a new 'linux,drconf-usable-memory'
property added by kexec-tools. Each entry in this property is of the
form of a count followed by that many (base, size) pairs for the above
mentioned regions. The number of cells in the count value is given by
the #size-cells property of the root node.
Signed-off-by: Chandru Siddalingappa <chandru@in.ibm.com>
Signed-off-by: Paul Mackerras <paulus@samba.org>
2008-08-29 18:28:16 +04:00
if ( is_kexec_kdump ) {
2017-12-01 19:47:08 +03:00
base = dt_mem_next_cell ( dt_root_addr_cells , usm ) ;
size = dt_mem_next_cell ( dt_root_size_cells , usm ) ;
}
if ( iommu_is_off ) {
if ( base > = 0x80000000ul )
[POWERPC] Support ibm,dynamic-reconfiguration-memory nodes
For PAPR partitions with large amounts of memory, the firmware has an
alternative, more compact representation for the information about the
memory in the partition and its NUMA associativity information. This
adds the code to the kernel to parse this alternative representation.
The other part of this patch is telling the firmware that we can
handle the alternative representation. There is however a subtlety
here, because the firmware will invoke a reboot if the memory
representation we request is different from the representation that
firmware is currently using. This is because firmware can't change
the representation on the fly. Further, some firmware versions used
on POWER5+ machines have a bug where this reboot leaves the machine
with an altered value of load-base, which will prevent any kernel
booting until it is reset to the normal value (0x4000). Because of
this bug, we do NOT set fake_elf.rpanote.new_mem_def = 1, and thus we
do not request the new representation on POWER5+ and earlier machines.
We do request the new representation on POWER6, which uses the
ibm,client-architecture-support call.
Signed-off-by: Paul Mackerras <paulus@samba.org>
2006-11-29 14:27:42 +03:00
continue ;
2017-12-01 19:47:08 +03:00
if ( ( base + size ) > 0x80000000ul )
size = 0x80000000ul - base ;
[POWERPC] Support ibm,dynamic-reconfiguration-memory nodes
For PAPR partitions with large amounts of memory, the firmware has an
alternative, more compact representation for the information about the
memory in the partition and its NUMA associativity information. This
adds the code to the kernel to parse this alternative representation.
The other part of this patch is telling the firmware that we can
handle the alternative representation. There is however a subtlety
here, because the firmware will invoke a reboot if the memory
representation we request is different from the representation that
firmware is currently using. This is because firmware can't change
the representation on the fly. Further, some firmware versions used
on POWER5+ machines have a bug where this reboot leaves the machine
with an altered value of load-base, which will prevent any kernel
booting until it is reset to the normal value (0x4000). Because of
this bug, we do NOT set fake_elf.rpanote.new_mem_def = 1, and thus we
do not request the new representation on POWER5+ and earlier machines.
We do request the new representation on POWER6, which uses the
ibm,client-architecture-support call.
Signed-off-by: Paul Mackerras <paulus@samba.org>
2006-11-29 14:27:42 +03:00
}
2017-12-01 19:47:08 +03:00
DBG ( " Adding: %llx -> %llx \n " , base , size ) ;
memblock_add ( base , size ) ;
} while ( - - rngs ) ;
[POWERPC] Support ibm,dynamic-reconfiguration-memory nodes
For PAPR partitions with large amounts of memory, the firmware has an
alternative, more compact representation for the information about the
memory in the partition and its NUMA associativity information. This
adds the code to the kernel to parse this alternative representation.
The other part of this patch is telling the firmware that we can
handle the alternative representation. There is however a subtlety
here, because the firmware will invoke a reboot if the memory
representation we request is different from the representation that
firmware is currently using. This is because firmware can't change
the representation on the fly. Further, some firmware versions used
on POWER5+ machines have a bug where this reboot leaves the machine
with an altered value of load-base, which will prevent any kernel
booting until it is reset to the normal value (0x4000). Because of
this bug, we do NOT set fake_elf.rpanote.new_mem_def = 1, and thus we
do not request the new representation on POWER5+ and earlier machines.
We do request the new representation on POWER6, which uses the
ibm,client-architecture-support call.
Signed-off-by: Paul Mackerras <paulus@samba.org>
2006-11-29 14:27:42 +03:00
}
# endif /* CONFIG_PPC_PSERIES */
2005-10-06 06:06:20 +04:00
2010-02-02 07:34:14 +03:00
static int __init early_init_dt_scan_memory_ppc ( unsigned long node ,
const char * uname ,
int depth , void * data )
2005-10-06 06:06:20 +04:00
{
2017-12-01 19:47:08 +03:00
# ifdef CONFIG_PPC_PSERIES
[POWERPC] Support ibm,dynamic-reconfiguration-memory nodes
For PAPR partitions with large amounts of memory, the firmware has an
alternative, more compact representation for the information about the
memory in the partition and its NUMA associativity information. This
adds the code to the kernel to parse this alternative representation.
The other part of this patch is telling the firmware that we can
handle the alternative representation. There is however a subtlety
here, because the firmware will invoke a reboot if the memory
representation we request is different from the representation that
firmware is currently using. This is because firmware can't change
the representation on the fly. Further, some firmware versions used
on POWER5+ machines have a bug where this reboot leaves the machine
with an altered value of load-base, which will prevent any kernel
booting until it is reset to the normal value (0x4000). Because of
this bug, we do NOT set fake_elf.rpanote.new_mem_def = 1, and thus we
do not request the new representation on POWER5+ and earlier machines.
We do request the new representation on POWER6, which uses the
ibm,client-architecture-support call.
Signed-off-by: Paul Mackerras <paulus@samba.org>
2006-11-29 14:27:42 +03:00
if ( depth = = 1 & &
2017-12-01 19:47:08 +03:00
strcmp ( uname , " ibm,dynamic-reconfiguration-memory " ) = = 0 ) {
walk_drmem_lmbs_early ( node , early_init_drmem_lmb ) ;
return 0 ;
}
# endif
2010-02-02 07:34:14 +03:00
return early_init_dt_scan_memory ( node , uname , depth , data ) ;
}
[POWERPC] Support ibm,dynamic-reconfiguration-memory nodes
For PAPR partitions with large amounts of memory, the firmware has an
alternative, more compact representation for the information about the
memory in the partition and its NUMA associativity information. This
adds the code to the kernel to parse this alternative representation.
The other part of this patch is telling the firmware that we can
handle the alternative representation. There is however a subtlety
here, because the firmware will invoke a reboot if the memory
representation we request is different from the representation that
firmware is currently using. This is because firmware can't change
the representation on the fly. Further, some firmware versions used
on POWER5+ machines have a bug where this reboot leaves the machine
with an altered value of load-base, which will prevent any kernel
booting until it is reset to the normal value (0x4000). Because of
this bug, we do NOT set fake_elf.rpanote.new_mem_def = 1, and thus we
do not request the new representation on POWER5+ and earlier machines.
We do request the new representation on POWER6, which uses the
ibm,client-architecture-support call.
Signed-off-by: Paul Mackerras <paulus@samba.org>
2006-11-29 14:27:42 +03:00
2013-12-24 11:12:08 +04:00
/*
* For a relocatable kernel , we need to get the memstart_addr first ,
* then use it to calculate the virtual kernel start address . This has
* to happen at a very early stage ( before machine_init ) . In this case ,
* we just want to get the memstart_address and would not like to mess the
* memblock at this stage . So introduce a variable to skip the memblock_add ( )
* for this reason .
*/
# ifdef CONFIG_RELOCATABLE
static int add_mem_to_memblock = 1 ;
# else
# define add_mem_to_memblock 1
# endif
2010-02-02 07:34:14 +03:00
void __init early_init_dt_add_memory_arch ( u64 base , u64 size )
{
2010-07-07 02:39:02 +04:00
# ifdef CONFIG_PPC64
2010-02-02 07:34:14 +03:00
if ( iommu_is_off ) {
if ( base > = 0x80000000ul )
return ;
if ( ( base + size ) > 0x80000000ul )
size = 0x80000000ul - base ;
}
2005-10-06 06:06:20 +04:00
# endif
2011-05-12 00:58:18 +04:00
/* Keep track of the beginning of memory -and- the size of
* the very first block in the device - tree as it represents
* the RMA on ppc64 server
*/
if ( base < memstart_addr ) {
memstart_addr = base ;
first_memblock_size = size ;
}
2010-07-07 02:39:02 +04:00
/* Add the chunk to the MEMBLOCK list */
2013-12-24 11:12:08 +04:00
if ( add_mem_to_memblock )
memblock_add ( base , size ) ;
2005-10-06 06:06:20 +04:00
}
2013-07-02 02:13:52 +04:00
static void __init early_reserve_mem_dt ( void )
2013-04-24 10:26:30 +04:00
{
2014-04-02 08:49:03 +04:00
unsigned long i , dt_root ;
int len ;
2013-04-24 10:26:30 +04:00
const __be32 * prop ;
2015-06-01 14:40:31 +03:00
early_init_fdt_reserve_self ( ) ;
2014-04-29 22:16:50 +04:00
early_init_fdt_scan_reserved_mem ( ) ;
2013-04-24 10:26:30 +04:00
dt_root = of_get_flat_dt_root ( ) ;
prop = of_get_flat_dt_prop ( dt_root , " reserved-ranges " , & len ) ;
if ( ! prop )
2013-07-02 02:13:52 +04:00
return ;
DBG ( " Found new-style reserved-ranges \n " ) ;
2013-04-24 10:26:30 +04:00
/* Each reserved range is an (address,size) pair, 2 cells each,
* totalling 4 cells per range . */
for ( i = 0 ; i < len / ( sizeof ( * prop ) * 4 ) ; i + + ) {
u64 base , size ;
base = of_read_number ( prop + ( i * 4 ) + 0 , 2 ) ;
size = of_read_number ( prop + ( i * 4 ) + 2 , 2 ) ;
2013-07-02 02:13:52 +04:00
if ( size ) {
DBG ( " reserving: %llx -> %llx \n " , base , size ) ;
2013-04-24 10:26:30 +04:00
memblock_reserve ( base , size ) ;
2013-07-02 02:13:52 +04:00
}
2013-04-24 10:26:30 +04:00
}
}
2005-10-06 06:06:20 +04:00
static void __init early_reserve_mem ( void )
{
2013-08-06 20:01:27 +04:00
__be64 * reserve_map ;
2005-10-06 06:06:20 +04:00
2013-08-06 20:01:27 +04:00
reserve_map = ( __be64 * ) ( ( ( unsigned long ) initial_boot_params ) +
2014-04-01 00:15:00 +04:00
fdt_off_mem_rsvmap ( initial_boot_params ) ) ;
2006-05-19 02:03:05 +04:00
2013-07-02 02:13:52 +04:00
/* Look for the new "reserved-regions" property in the DT */
early_reserve_mem_dt ( ) ;
2013-04-24 10:26:30 +04:00
2007-02-28 06:12:29 +03:00
# ifdef CONFIG_BLK_DEV_INITRD
2013-07-02 02:13:52 +04:00
/* Then reserve the initrd, if any */
if ( initrd_start & & ( initrd_end > initrd_start ) ) {
powerpc: Force page alignment for initrd reserved memory
When using 64K pages with a separate cpio rootfs, U-Boot will align
the rootfs on a 4K page boundary. When the memory is reserved, and
subsequent early memblock_alloc is called, it will allocate memory
between the 64K page alignment and reserved memory. When the reserved
memory is subsequently freed, it is done so by pages, causing the
early memblock_alloc requests to be re-used, which in my case, caused
the device-tree to be clobbered.
This patch forces the reserved memory for initrd to be kernel page
aligned, and will move the device tree if it overlaps with the range
extension of initrd. This patch will also consolidate the identical
function free_initrd_mem() from mm/init_32.c, init_64.c to mm/mem.c,
and adds the same range extension when freeing initrd. free_initrd_mem()
is also moved to the __init section.
Many thanks to Milton Miller for his input on this patch.
[BenH: Fixed build without CONFIG_BLK_DEV_INITRD]
Signed-off-by: Dave Carroll <dcarroll@astekcorp.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
2011-06-09 10:52:38 +04:00
memblock_reserve ( _ALIGN_DOWN ( __pa ( initrd_start ) , PAGE_SIZE ) ,
_ALIGN_UP ( initrd_end , PAGE_SIZE ) -
_ALIGN_DOWN ( initrd_start , PAGE_SIZE ) ) ;
2013-07-02 02:13:52 +04:00
}
2007-02-28 06:12:29 +03:00
# endif /* CONFIG_BLK_DEV_INITRD */
2006-01-12 02:57:13 +03:00
# ifdef CONFIG_PPC32
/*
* Handle the case where we might be booting from an old kexec
* image that setup the mem_rsvmap as pairs of 32 - bit values
*/
2013-08-06 20:01:27 +04:00
if ( be64_to_cpup ( reserve_map ) > 0xffffffffull ) {
2006-01-12 02:57:13 +03:00
u32 base_32 , size_32 ;
2013-08-06 20:01:27 +04:00
__be32 * reserve_map_32 = ( __be32 * ) reserve_map ;
2006-01-12 02:57:13 +03:00
2013-07-02 02:13:52 +04:00
DBG ( " Found old 32-bit reserve map \n " ) ;
2006-01-12 02:57:13 +03:00
while ( 1 ) {
2013-08-06 20:01:27 +04:00
base_32 = be32_to_cpup ( reserve_map_32 + + ) ;
size_32 = be32_to_cpup ( reserve_map_32 + + ) ;
2006-01-12 02:57:13 +03:00
if ( size_32 = = 0 )
break ;
2006-02-24 19:54:52 +03:00
DBG ( " reserving: %x -> %x \n " , base_32 , size_32 ) ;
2010-07-12 08:36:09 +04:00
memblock_reserve ( base_32 , size_32 ) ;
2006-01-12 02:57:13 +03:00
}
return ;
}
# endif
2005-10-06 06:06:20 +04:00
}
2017-10-12 13:17:16 +03:00
# ifdef CONFIG_PPC_TRANSACTIONAL_MEM
static bool tm_disabled __initdata ;
static int __init parse_ppc_tm ( char * str )
{
bool res ;
if ( kstrtobool ( str , & res ) )
return - EINVAL ;
tm_disabled = ! res ;
return 0 ;
}
early_param ( " ppc_tm " , parse_ppc_tm ) ;
static void __init tm_init ( void )
{
if ( tm_disabled ) {
pr_info ( " Disabling hardware transactional memory (HTM) \n " ) ;
cur_cpu_spec - > cpu_user_features2 & =
~ ( PPC_FEATURE2_HTM_NOSC | PPC_FEATURE2_HTM ) ;
cur_cpu_spec - > cpu_features & = ~ CPU_FTR_TM ;
2017-10-12 13:17:18 +03:00
return ;
2017-10-12 13:17:16 +03:00
}
2017-10-12 13:17:18 +03:00
pnv_tm_init ( ) ;
2017-10-12 13:17:16 +03:00
}
# else
static void tm_init ( void ) { }
# endif /* CONFIG_PPC_TRANSACTIONAL_MEM */
2005-10-06 06:06:20 +04:00
void __init early_init_devtree ( void * params )
{
2009-05-08 16:19:27 +04:00
phys_addr_t limit ;
2008-11-26 19:19:26 +03:00
2007-06-16 02:06:14 +04:00
DBG ( " -> early_init_devtree(%p) \n " , params ) ;
2005-10-06 06:06:20 +04:00
2014-08-28 12:40:47 +04:00
/* Too early to BUG_ON(), do it by hand */
if ( ! early_init_dt_verify ( params ) )
panic ( " BUG: Failed verifying flat device tree, bad version? " ) ;
2006-06-23 12:20:13 +04:00
# ifdef CONFIG_PPC_RTAS
/* Some machines might need RTAS info for debugging, grab it now. */
of_scan_flat_dt ( early_init_dt_scan_rtas , NULL ) ;
# endif
2011-09-19 21:44:57 +04:00
# ifdef CONFIG_PPC_POWERNV
/* Some machines might need OPAL info for debugging, grab it now. */
of_scan_flat_dt ( early_init_dt_scan_opal , NULL ) ;
# endif
2012-02-16 05:14:22 +04:00
# ifdef CONFIG_FA_DUMP
/* scan tree to see if dump is active during last boot */
of_scan_flat_dt ( early_init_dt_scan_fw_dump , NULL ) ;
# endif
2005-10-06 06:06:20 +04:00
/* Retrieve various informations from the /chosen node of the
* device - tree , including the platform type , initrd location and
* size , TCE reserve , and more . . .
*/
2014-09-17 08:39:36 +04:00
of_scan_flat_dt ( early_init_dt_scan_chosen_ppc , boot_command_line ) ;
2005-10-06 06:06:20 +04:00
2010-07-12 08:36:09 +04:00
/* Scan memory nodes and rebuild MEMBLOCKs */
2005-11-07 03:06:55 +03:00
of_scan_flat_dt ( early_init_dt_scan_root , NULL ) ;
2010-02-02 07:34:14 +03:00
of_scan_flat_dt ( early_init_dt_scan_memory_ppc , NULL ) ;
2006-05-17 12:00:45 +04:00
parse_early_param ( ) ;
2011-09-16 19:39:58 +04:00
/* make sure we've parsed cmdline for mem= before this */
if ( memory_limit )
2012-08-21 05:42:33 +04:00
first_memblock_size = min_t ( u64 , first_memblock_size , memory_limit ) ;
2011-09-16 19:39:58 +04:00
setup_initial_memory_limit ( memstart_addr , first_memblock_size ) ;
2010-07-12 08:36:09 +04:00
/* Reserve MEMBLOCK regions used by kernel, initrd, dt, etc... */
memblock_reserve ( PHYSICAL_START , __pa ( klimit ) - PHYSICAL_START ) ;
powerpc: Make the 64-bit kernel as a position-independent executable
This implements CONFIG_RELOCATABLE for 64-bit by making the kernel as
a position-independent executable (PIE) when it is set. This involves
processing the dynamic relocations in the image in the early stages of
booting, even if the kernel is being run at the address it is linked at,
since the linker does not necessarily fill in words in the image for
which there are dynamic relocations. (In fact the linker does fill in
such words for 64-bit executables, though not for 32-bit executables,
so in principle we could avoid calling relocate() entirely when we're
running a 64-bit kernel at the linked address.)
The dynamic relocations are processed by a new function relocate(addr),
where the addr parameter is the virtual address where the image will be
run. In fact we call it twice; once before calling prom_init, and again
when starting the main kernel. This means that reloc_offset() returns
0 in prom_init (since it has been relocated to the address it is running
at), which necessitated a few adjustments.
This also changes __va and __pa to use an equivalent definition that is
simpler. With the relocatable kernel, PAGE_OFFSET and MEMORY_START are
constants (for 64-bit) whereas PHYSICAL_START is a variable (and
KERNELBASE ideally should be too, but isn't yet).
With this, relocatable kernels still copy themselves down to physical
address 0 and run there.
Signed-off-by: Paul Mackerras <paulus@samba.org>
2008-08-30 05:43:47 +04:00
/* If relocatable, reserve first 32k for interrupt vectors etc. */
if ( PHYSICAL_START > MEMORY_START )
2010-07-12 08:36:09 +04:00
memblock_reserve ( MEMORY_START , 0x8000 ) ;
2006-05-17 12:00:49 +04:00
reserve_kdump_trampoline ( ) ;
2012-02-16 05:14:22 +04:00
# ifdef CONFIG_FA_DUMP
/*
* If we fail to reserve memory for firmware - assisted dump then
* fallback to kexec based kdump .
*/
if ( fadump_reserve_mem ( ) = = 0 )
# endif
reserve_crashkernel ( ) ;
2005-10-06 06:06:20 +04:00
early_reserve_mem ( ) ;
2014-09-17 16:15:34 +04:00
/* Ensure that total memory size is page-aligned. */
2011-12-08 22:22:07 +04:00
limit = ALIGN ( memory_limit ? : memblock_phys_mem_size ( ) , PAGE_SIZE ) ;
2010-07-12 08:36:09 +04:00
memblock_enforce_memory_limit ( limit ) ;
2008-11-26 19:19:26 +03:00
2011-12-08 22:22:08 +04:00
memblock_allow_resize ( ) ;
2010-07-12 08:36:09 +04:00
memblock_dump_all ( ) ;
2006-05-17 12:00:46 +04:00
2010-07-12 08:36:09 +04:00
DBG ( " Phys. mem: %llx \n " , memblock_phys_mem_size ( ) ) ;
2006-05-17 12:00:46 +04:00
/* We may need to relocate the flat tree, do it now.
* FIXME . . and the initrd too ? */
move_device_tree ( ) ;
2018-02-13 18:08:19 +03:00
allocate_paca_ptrs ( ) ;
2010-01-28 16:23:22 +03:00
2005-10-06 06:06:20 +04:00
DBG ( " Scanning CPUs ... \n " ) ;
2017-05-09 06:16:52 +03:00
dt_cpu_ftrs_scan ( ) ;
2011-03-31 05:57:33 +04:00
/* Retrieve CPU related informations from the flat tree
2005-11-07 03:06:55 +03:00
* ( altivec support , boot CPU ID , . . . )
2005-10-06 06:06:20 +04:00
*/
2005-11-07 03:06:55 +03:00
of_scan_flat_dt ( early_init_dt_scan_cpus , NULL ) ;
2014-03-28 06:36:27 +04:00
if ( boot_cpuid < 0 ) {
2015-02-27 17:52:31 +03:00
printk ( " Failed to identify boot CPU ! \n " ) ;
2014-03-28 06:36:27 +04:00
BUG ( ) ;
}
2005-10-06 06:06:20 +04:00
2011-05-25 22:09:12 +04:00
# if defined(CONFIG_SMP) && defined(CONFIG_PPC64)
/* We'll later wait for secondaries to check in; there are
* NCPUS - 1 non - boot CPUs : - )
*/
spinning_secondaries = boot_cpu_count - 1 ;
# endif
2016-07-26 13:09:30 +03:00
mmu_early_init_devtree ( ) ;
2013-12-16 09:16:24 +04:00
# ifdef CONFIG_PPC_POWERNV
/* Scan and build the list of machine check recoverable ranges */
of_scan_flat_dt ( early_init_dt_scan_recoverable_ranges , NULL ) ;
# endif
2016-07-05 08:03:44 +03:00
epapr_paravirt_early_init ( ) ;
2013-12-16 09:16:24 +04:00
2016-07-05 08:03:48 +03:00
/* Now try to figure out if we are running on LPAR and so on */
pseries_probe_fw_features ( ) ;
2016-07-05 08:03:51 +03:00
# ifdef CONFIG_PPC_PS3
/* Identify PS3 firmware */
if ( of_flat_dt_is_compatible ( of_get_flat_dt_root ( ) , " sony,ps3 " ) )
powerpc_firmware_features | = FW_FEATURE_PS3_POSSIBLE ;
# endif
2017-10-12 13:17:16 +03:00
tm_init ( ) ;
2005-10-06 06:06:20 +04:00
DBG ( " <- early_init_devtree() \n " ) ;
}
2013-12-24 11:12:08 +04:00
# ifdef CONFIG_RELOCATABLE
/*
* This function run before early_init_devtree , so we have to init
* initial_boot_params .
*/
void __init early_get_first_memblock_info ( void * params , phys_addr_t * size )
{
/* Setup flat device-tree pointer */
initial_boot_params = params ;
/*
* Scan the memory nodes and set add_mem_to_memblock to 0 to avoid
* mess the memblock .
*/
add_mem_to_memblock = 0 ;
of_scan_flat_dt ( early_init_dt_scan_root , NULL ) ;
of_scan_flat_dt ( early_init_dt_scan_memory_ppc , NULL ) ;
add_mem_to_memblock = 1 ;
if ( size )
* size = first_memblock_size ;
}
# endif
2005-10-06 06:06:20 +04:00
/*******
*
* New implementation of the OF " find " APIs , return a refcounted
* object , call of_node_put ( ) when done . The device tree and list
* are protected by a rw_lock .
*
* Note that property management will need some locking as well ,
* this isn ' t dealt with yet .
*
* * * * * * */
2013-07-15 07:03:10 +04:00
/**
* of_get_ibm_chip_id - Returns the IBM " chip-id " of a device
* @ np : device node of the device
*
* This looks for a property " ibm,chip-id " in the node or any
* of its parents and returns its content , or - 1 if it cannot
* be found .
*/
int of_get_ibm_chip_id ( struct device_node * np )
{
of_node_get ( np ) ;
2015-10-17 00:38:45 +03:00
while ( np ) {
u32 chip_id ;
2013-07-15 07:03:10 +04:00
2015-10-17 00:38:45 +03:00
/*
* Skiboot may produce memory nodes that contain more than one
* cell in chip - id , we only read the first one here .
*/
if ( ! of_property_read_u32 ( np , " ibm,chip-id " , & chip_id ) ) {
2013-07-15 07:03:10 +04:00
of_node_put ( np ) ;
2015-10-17 00:38:45 +03:00
return chip_id ;
2013-07-15 07:03:10 +04:00
}
2015-10-26 03:48:46 +03:00
np = of_get_next_parent ( np ) ;
2013-07-15 07:03:10 +04:00
}
return - 1 ;
}
2015-05-07 20:49:12 +03:00
EXPORT_SYMBOL ( of_get_ibm_chip_id ) ;
2013-07-15 07:03:10 +04:00
2013-11-20 04:05:01 +04:00
/**
* cpu_to_chip_id - Return the cpus chip - id
* @ cpu : The logical cpu number .
*
* Return the value of the ibm , chip - id property corresponding to the given
* logical cpu number . If the chip - id can not be found , returns - 1.
*/
int cpu_to_chip_id ( int cpu )
{
struct device_node * np ;
np = of_get_cpu_node ( cpu , NULL ) ;
if ( ! np )
return - 1 ;
of_node_put ( np ) ;
return of_get_ibm_chip_id ( np ) ;
}
EXPORT_SYMBOL ( cpu_to_chip_id ) ;
2013-08-15 16:34:18 +04:00
bool arch_match_cpu_phys_id ( int cpu , u64 phys_id )
{
2018-02-13 18:08:18 +03:00
# ifdef CONFIG_SMP
/*
* Early firmware scanning must use this rather than
* get_hard_smp_processor_id because we don ' t have pacas allocated
* until memory topology is discovered .
*/
if ( cpu_to_phys_id ! = NULL )
return ( int ) phys_id = = cpu_to_phys_id [ cpu ] ;
# endif
2013-08-15 16:34:18 +04:00
return ( int ) phys_id = = get_hard_smp_processor_id ( cpu ) ;
}