Re: [linux-yocto] [kernel-cache yocto-5.2/master] [PATCH] ti-am335x: enable GCC -O2 optimization
On Thu, Oct 31, 2019 at 11:12 PM He Zhe wrote: > > Hi Bruce, > > This now happens on qemuarmv5 and possibly on all arm arches. > > standard.scc -> arm.scc -> arm.cfg -> CONFIG_CC_OPTIMIZE_FOR_SIZE=y > > It hangs the whole system. > But turning off CONFIG_CC_OPTIMIZE_FOR_SIZE would affect all arches. > > What do you think? It used to be the opposite. The boards only booted with this enabled. So my worry about changing it globally is that I fix some boards, and break others. We can always just change the setting in the BSP .cfg's that we can prove they build and boot. Bruce > > Thanks, > Zhe > > > On 10/30/19 8:25 AM, Bruce Ashfield wrote: > > merged. > > > > We should also either have a plan to figure out the root cause > > of this, or we should patch the Kconfig to be broken if enabled > > .. that way we'll prevent others from turning it on by mistake. > > > > > > Bruce > > > > > > In message: [linux-yocto] [kernel-cache yocto-5.2/master] [PATCH] > > ti-am335x: enable GCC -O2 optimization > > on 29/10/2019 Jun Miao wrote: > > > >> Ti-am335x bsp includes the standard.scc file, which will set > >> CONFIG_CC_OPTIMIZE_FOR_SIZE=y. > >> As a result, the system boot hangs like below in v5.4.0-rc4 kernel version: > >> When we enable CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE for -O2 Optimization > >> level, > >> the boot succeeds. > >> > >> boot log: > >> systemd[1]: Set hostname to . > >> systemd[1]: Failed to open netlink: Operation not permitted > >> systemd-fstab-generator[120]: Failed to write unit file -.mount: Bad > >> address > >> systemd-fstab-generator[120]: Failed to write unit file > >> var-volatile.mount: Bad address > >> ... ... > >> systemd[1]: Failed to start device monitor: Bad address > >> systemd[1]: SO_PASSCRED failed: Bad address > >> [!!] Failed to start up manager. > >> systemd[1]: Freezing execution. > >> > >> Signed-off-by: Jun Miao > >> --- > >> bsp/ti-am335x/ti-am335x.cfg | 2 ++ > >> 1 file changed, 2 insertions(+) > >> > >> diff --git a/bsp/ti-am335x/ti-am335x.cfg b/bsp/ti-am335x/ti-am335x.cfg > >> index 71884fd7..190cb876 100644 > >> --- a/bsp/ti-am335x/ti-am335x.cfg > >> +++ b/bsp/ti-am335x/ti-am335x.cfg > >> @@ -258,3 +258,5 @@ CONFIG_OMAP_CONTROL_PHY=y > >> > >> CONFIG_TI_PIPE3=y > >> CONFIG_ARM_PMU=y > >> + > >> +CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y > >> -- > >> 2.17.1 > >> > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [kernel-cache yocto-5.2/master] [PATCH] ti-am335x: enable GCC -O2 optimization
Hi Bruce, This now happens on qemuarmv5 and possibly on all arm arches. standard.scc -> arm.scc -> arm.cfg -> CONFIG_CC_OPTIMIZE_FOR_SIZE=y It hangs the whole system. But turning off CONFIG_CC_OPTIMIZE_FOR_SIZE would affect all arches. What do you think? Thanks, Zhe On 10/30/19 8:25 AM, Bruce Ashfield wrote: > merged. > > We should also either have a plan to figure out the root cause > of this, or we should patch the Kconfig to be broken if enabled > .. that way we'll prevent others from turning it on by mistake. > > > Bruce > > > In message: [linux-yocto] [kernel-cache yocto-5.2/master] [PATCH] ti-am335x: > enable GCC -O2 optimization > on 29/10/2019 Jun Miao wrote: > >> Ti-am335x bsp includes the standard.scc file, which will set >> CONFIG_CC_OPTIMIZE_FOR_SIZE=y. >> As a result, the system boot hangs like below in v5.4.0-rc4 kernel version: >> When we enable CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE for -O2 Optimization level, >> the boot succeeds. >> >> boot log: >> systemd[1]: Set hostname to . >> systemd[1]: Failed to open netlink: Operation not permitted >> systemd-fstab-generator[120]: Failed to write unit file -.mount: Bad address >> systemd-fstab-generator[120]: Failed to write unit file var-volatile.mount: >> Bad address >> ... ... >> systemd[1]: Failed to start device monitor: Bad address >> systemd[1]: SO_PASSCRED failed: Bad address >> [!!] Failed to start up manager. >> systemd[1]: Freezing execution. >> >> Signed-off-by: Jun Miao >> --- >> bsp/ti-am335x/ti-am335x.cfg | 2 ++ >> 1 file changed, 2 insertions(+) >> >> diff --git a/bsp/ti-am335x/ti-am335x.cfg b/bsp/ti-am335x/ti-am335x.cfg >> index 71884fd7..190cb876 100644 >> --- a/bsp/ti-am335x/ti-am335x.cfg >> +++ b/bsp/ti-am335x/ti-am335x.cfg >> @@ -258,3 +258,5 @@ CONFIG_OMAP_CONTROL_PHY=y >> >> CONFIG_TI_PIPE3=y >> CONFIG_ARM_PMU=y >> + >> +CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y >> -- >> 2.17.1 >> -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [kernel-cache yocto-5.2/master] [PATCH] ti-am335x: enable GCC -O2 optimization
merged. We should also either have a plan to figure out the root cause of this, or we should patch the Kconfig to be broken if enabled .. that way we'll prevent others from turning it on by mistake. Bruce In message: [linux-yocto] [kernel-cache yocto-5.2/master] [PATCH] ti-am335x: enable GCC -O2 optimization on 29/10/2019 Jun Miao wrote: > Ti-am335x bsp includes the standard.scc file, which will set > CONFIG_CC_OPTIMIZE_FOR_SIZE=y. > As a result, the system boot hangs like below in v5.4.0-rc4 kernel version: > When we enable CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE for -O2 Optimization level, > the boot succeeds. > > boot log: > systemd[1]: Set hostname to . > systemd[1]: Failed to open netlink: Operation not permitted > systemd-fstab-generator[120]: Failed to write unit file -.mount: Bad address > systemd-fstab-generator[120]: Failed to write unit file var-volatile.mount: > Bad address > ... ... > systemd[1]: Failed to start device monitor: Bad address > systemd[1]: SO_PASSCRED failed: Bad address > [!!] Failed to start up manager. > systemd[1]: Freezing execution. > > Signed-off-by: Jun Miao > --- > bsp/ti-am335x/ti-am335x.cfg | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/bsp/ti-am335x/ti-am335x.cfg b/bsp/ti-am335x/ti-am335x.cfg > index 71884fd7..190cb876 100644 > --- a/bsp/ti-am335x/ti-am335x.cfg > +++ b/bsp/ti-am335x/ti-am335x.cfg > @@ -258,3 +258,5 @@ CONFIG_OMAP_CONTROL_PHY=y > > CONFIG_TI_PIPE3=y > CONFIG_ARM_PMU=y > + > +CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y > -- > 2.17.1 > -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [kernel-cache yocto-5.2/master] [PATCH] ti-am335x: enable GCC -O2 optimization
Ti-am335x bsp includes the standard.scc file, which will set CONFIG_CC_OPTIMIZE_FOR_SIZE=y. As a result, the system boot hangs like below in v5.4.0-rc4 kernel version: When we enable CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE for -O2 Optimization level, the boot succeeds. boot log: systemd[1]: Set hostname to . systemd[1]: Failed to open netlink: Operation not permitted systemd-fstab-generator[120]: Failed to write unit file -.mount: Bad address systemd-fstab-generator[120]: Failed to write unit file var-volatile.mount: Bad address ... ... systemd[1]: Failed to start device monitor: Bad address systemd[1]: SO_PASSCRED failed: Bad address [!!] Failed to start up manager. systemd[1]: Freezing execution. Signed-off-by: Jun Miao --- bsp/ti-am335x/ti-am335x.cfg | 2 ++ 1 file changed, 2 insertions(+) diff --git a/bsp/ti-am335x/ti-am335x.cfg b/bsp/ti-am335x/ti-am335x.cfg index 71884fd7..190cb876 100644 --- a/bsp/ti-am335x/ti-am335x.cfg +++ b/bsp/ti-am335x/ti-am335x.cfg @@ -258,3 +258,5 @@ CONFIG_OMAP_CONTROL_PHY=y CONFIG_TI_PIPE3=y CONFIG_ARM_PMU=y + +CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y -- 2.17.1 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
