Shuah Khan writes:
> On 5/20/24 20:26, Michael Ellerman wrote:
>> Fix build error on ppc64:
>>dev_in_maps.c: In function ‘get_file_dev_and_inode’:
>>dev_in_maps.c:60:59: error: format ‘%llu’ expects argument of type
>>‘long long unsigned int *’, but argumen
On 5/20/24 20:26, Michael Ellerman wrote:
Fix build error on ppc64:
dev_in_maps.c: In function ‘get_file_dev_and_inode’:
dev_in_maps.c:60:59: error: format ‘%llu’ expects argument of type
‘long long unsigned int *’, but argument 7 has type ‘__u64 *’ {aka ‘long
unsigned int
Fix build error on ppc64:
dev_in_maps.c: In function ‘get_file_dev_and_inode’:
dev_in_maps.c:60:59: error: format ‘%llu’ expects argument of type
‘long long unsigned int *’, but argument 7 has type ‘__u64 *’ {aka ‘long
unsigned int *’} [-Werror=format=]
By switching to unsigned long long
From: Michael Ellerman
[ Upstream commit f8d3555355653848082c351fa90775214fb8a4fa ]
With CONFIG_GENERIC_BUG=n the build fails with:
arch/powerpc/kernel/traps.c:1442:5: error: no previous prototype for
‘is_valid_bugaddr’ [-Werror=missing-prototypes]
1442 | int is_valid_bugaddr(unsigned long
From: Michael Ellerman
[ Upstream commit f8d3555355653848082c351fa90775214fb8a4fa ]
With CONFIG_GENERIC_BUG=n the build fails with:
arch/powerpc/kernel/traps.c:1442:5: error: no previous prototype for
‘is_valid_bugaddr’ [-Werror=missing-prototypes]
1442 | int is_valid_bugaddr(unsigned long
From: Michael Ellerman
[ Upstream commit f8d3555355653848082c351fa90775214fb8a4fa ]
With CONFIG_GENERIC_BUG=n the build fails with:
arch/powerpc/kernel/traps.c:1442:5: error: no previous prototype for
‘is_valid_bugaddr’ [-Werror=missing-prototypes]
1442 | int is_valid_bugaddr(unsigned long
From: Michael Ellerman
[ Upstream commit f8d3555355653848082c351fa90775214fb8a4fa ]
With CONFIG_GENERIC_BUG=n the build fails with:
arch/powerpc/kernel/traps.c:1442:5: error: no previous prototype for
‘is_valid_bugaddr’ [-Werror=missing-prototypes]
1442 | int is_valid_bugaddr(unsigned long
From: Michael Ellerman
[ Upstream commit f8d3555355653848082c351fa90775214fb8a4fa ]
With CONFIG_GENERIC_BUG=n the build fails with:
arch/powerpc/kernel/traps.c:1442:5: error: no previous prototype for
‘is_valid_bugaddr’ [-Werror=missing-prototypes]
1442 | int is_valid_bugaddr(unsigned long
From: Michael Ellerman
[ Upstream commit f8d3555355653848082c351fa90775214fb8a4fa ]
With CONFIG_GENERIC_BUG=n the build fails with:
arch/powerpc/kernel/traps.c:1442:5: error: no previous prototype for
‘is_valid_bugaddr’ [-Werror=missing-prototypes]
1442 | int is_valid_bugaddr(unsigned long
From: Michael Ellerman
[ Upstream commit f8d3555355653848082c351fa90775214fb8a4fa ]
With CONFIG_GENERIC_BUG=n the build fails with:
arch/powerpc/kernel/traps.c:1442:5: error: no previous prototype for
‘is_valid_bugaddr’ [-Werror=missing-prototypes]
1442 | int is_valid_bugaddr(unsigned long
With CONFIG_GENERIC_BUG=n the build fails with:
arch/powerpc/kernel/traps.c:1442:5: error: no previous prototype for
‘is_valid_bugaddr’ [-Werror=missing-prototypes]
1442 | int is_valid_bugaddr(unsigned long addr)
| ^~~~
The prototype is only defined, and the function i
On Mon, 28 Aug 2023 13:16:57 +0530, Aneesh Kumar K.V wrote:
> With CONFIG_SPARSEMEM disabled the below kernel build error is observed.
>
> arch/powerpc/mm/init_64.c:477:38: error: use of undeclared identifier
> 'SECTION_SIZE_BITS'
>
> CONFIG_MEMORY_HOTPLUG depends o
On 8/28/23 1:16 PM, Aneesh Kumar K.V wrote:
> With CONFIG_SPARSEMEM disabled the below kernel build error is observed.
>
> arch/powerpc/mm/init_64.c:477:38: error: use of undeclared identifier
> 'SECTION_SIZE_BITS'
>
> CONFIG_MEMORY_HOTPLUG depends on CONFIG_SPARSEM
With CONFIG_SPARSEMEM disabled the below kernel build error is observed.
arch/powerpc/mm/init_64.c:477:38: error: use of undeclared identifier
'SECTION_SIZE_BITS'
CONFIG_MEMORY_HOTPLUG depends on CONFIG_SPARSEMEM and it is more clear
to describe the code dependency in terms of MEMO
cognized opcode: `stbcx.'
> make[5]: *** [scripts/Makefile.build:252:
> arch/powerpc/mm/nohash/e500_hugetlbpage.o] Error 1
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/nohash: Fix build error with binutils >= 2.38
https://git.kernel.org/powerpc/c/91360b446a5cced537d61fc2394253e8c6b9ae7b
cheers
With bintils >= 2.38 the ppc64_book3e_allmodconfig build fails:
{standard input}: Assembler messages:
{standard input}:196: Error: unrecognized opcode: `lbarx'
{standard input}:196: Error: unrecognized opcode: `stbcx.'
make[5]: *** [scripts/Makefile.build:252:
arch/powerpc/mm/nohash/e500_
are_has_feature(FW_FEATURE_LPAR))
> | ^~~~
>
> Add a direct include of asm/firmware.h to fix the error.
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/64e: Fix kexec build error
https://git.kernel.org/powerpc/c/4cfa6ff24a9744ba484521c38bea613134fbfcb3
cheers
When building ppc64_book3e_allmodconfig the build fails with:
arch/powerpc/kexec/file_load_64.c:1063:14: error: implicit declaration of
function ‘firmware_has_feature’
1063 | if (!firmware_has_feature(FW_FEATURE_LPAR))
| ^~~~
Add a direct include
Laurent Dufour writes:
> Le 27/07/2022 à 13:38, Michael Ellerman a écrit :
>> Laurent Dufour writes:
>>> Sachin reported the following build error when CONFIG_SOFTLOCKUP_DETECTOR
>>> is not set:
>>>
>>> kernel/watchdog.c:597:20: error: static dec
Le 27/07/2022 à 13:38, Michael Ellerman a écrit :
> Laurent Dufour writes:
>> Sachin reported the following build error when CONFIG_SOFTLOCKUP_DETECTOR
>> is not set:
>>
>> kernel/watchdog.c:597:20: error: static declaration of
>> 'lockup_detector_recon
Laurent Dufour writes:
> Sachin reported the following build error when CONFIG_SOFTLOCKUP_DETECTOR
> is not set:
>
> kernel/watchdog.c:597:20: error: static declaration of
> 'lockup_detector_reconfigure' follows non-static declaration
> static inline void lock
> The definition of lockup_detector_reconfigure should be exported even in
> that case, and __lockup_detector_reconfigure should remain static.
>
> Fixes: 24a1260705b7 ("watchdog: export lockup_detector_reconfigure")
> Reported-by: Sachin Sant
> Signed-off-by: Laurent Dufour
> ---
> kernel/wat
Sachin reported the following build error when CONFIG_SOFTLOCKUP_DETECTOR
is not set:
kernel/watchdog.c:597:20: error: static declaration of
'lockup_detector_reconfigure' follows non-static declaration
static inline void lockup_detector_reconf
declaration of
> function ‘of_read_number’; did you mean ‘seq_read_iter’?
> [-Werror=implicit-function-declaration]
> start = of_read_number(prop, len / 4);
> ^~
> seq_read_iter
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/kaslr_boo
-declaration]
> early_get_first_memblock_info(__va(dt_ptr), &size);
> ^
>
> Add missing include file linux/of_fdt.h to fix this.
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/book3e: Fix build error
https://git.kernel.org/powerpc/c/7574dd080ee0a1e8a9c6312dc7c8fe97f73415ff
cheers
YueHaibing writes:
> On 2022/5/17 18:45, Christophe Leroy wrote:
>> Le 17/05/2022 à 11:48, YueHaibing a écrit :
>>> arch/powerpc/mm/nohash/fsl_book3e.c: In function ‘relocate_init’:
>>> arch/powerpc/mm/nohash/fsl_book3e.c:348:2: error: implicit declaration of
>>> function ‘early_get_first_membloc
Le 17/05/2022 à 11:48, YueHaibing a écrit :
> arch/powerpc/mm/nohash/fsl_book3e.c: In function ‘relocate_init’:
> arch/powerpc/mm/nohash/fsl_book3e.c:348:2: error: implicit declaration of
> function ‘early_get_first_memblock_info’
> [-Werror=implicit-function-declaration]
>early_get_first_m
On Sat, May 07, 2022 at 02:22:43PM +0900, Masahiro Yamada wrote:
> When I refactored this Makefile, I accidentally changed the CONFIG
> option.
>
> Fixes: b52455a73db9 ("crypto: vmx - Align the short log with Makefile
> cleanups")
> Reported-by: kernel test robot
> Signed-off-by: Masahiro Yamada
When I refactored this Makefile, I accidentally changed the CONFIG
option.
Fixes: b52455a73db9 ("crypto: vmx - Align the short log with Makefile cleanups")
Reported-by: kernel test robot
Signed-off-by: Masahiro Yamada
---
drivers/crypto/vmx/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 de
On Fri, 11 Feb 2022 01:51:13 +0100, Anders Roxell wrote:
> Building tinyconfig with gcc (Debian 11.2.0-16) and assembler (Debian
> 2.37.90.20220207) the following build error shows up:
>
> {standard input}: Assembler messages:
> {standard input}:2088: Error: unrecognized opcode: `
Building tinyconfig with gcc (Debian 11.2.0-16) and assembler (Debian
2.37.90.20220207) the following build error shows up:
{standard input}: Assembler messages:
{standard input}:2088: Error: unrecognized opcode: `ptesync'
make[3]: *** [/builds/linux/scripts/Makefile.build:287:
arch/powerp
Le 10/02/2022 à 13:44, Anders Roxell a écrit :
> Building tinyconfig with gcc (Debian 11.2.0-16) and assembler (Debian
> 2.37.90.20220207) the following build error shows up:
>
> {standard input}: Assembler messages:
> {standard input}:2088: Error: unrecognized opcode: `pt
Building tinyconfig with gcc (Debian 11.2.0-16) and assembler (Debian
2.37.90.20220207) the following build error shows up:
{standard input}: Assembler messages:
{standard input}:2088: Error: unrecognized opcode: `ptesync'
make[3]: *** [/builds/linux/scripts/Makefile.build:287:
arch/powerp
It booted at least. I'll try your suggestions as soon as I can, I'm
progressing slower than ever, concentration is somewhat lapse still
Thanks.
Best regards
Michael
On Tue, Jan 11, 2022, 10:51 Christophe Leroy
wrote:
>
>
> Le 11/01/2022 à 10:32, Mike a écrit :
> > I managed to fix it in the
Hmm, why on earth did it historically compile though, from what I gathered
before my hand fell off, -maltivec was removed from arch/powerpc/mm, I ran
out of hard drive compiling ofc. but it seems happy,
>Also please prefer CONFIG_PPC64 to __powerpc64__
Copy pasted the style in of the file... I u
Le 11/01/2022 à 10:32, Mike a écrit :
> I managed to fix it in the end, patch attached, though i should have
> done a $(call cc-option-, -maltivec, -mabi=altivec) in the
> arch/powerpc/mm/Makefile
> I wrongly assumed that the manual i had downloaded at 4.44am was for
> 32bit ppc only and found
Le 10/01/2022 à 13:32, Mike a écrit :
> Hey, so I originally sat down to compile the fast headers V2 patch, but
> quickly discovered other things at play, and grabbed 5.16.0 a few hours
> after it lifted off, arch/powerpc/mm/mmu_context.c I had to
> specifically say had to include -maltivec o
Hey, so I originally sat down to compile the fast headers V2 patch, but
quickly discovered other things at play, and grabbed 5.16.0 a few hours
after it lifted off, arch/powerpc/mm/mmu_context.c I had to specifically
say had to include -maltivec or it barfed on a 'dssall', I'm fine with
that, I've
Le 27/08/2021 à 15:15, Michael Ellerman a écrit :
On Mon, 16 Aug 2021 14:10:32 +1000, Michael Ellerman wrote:
As reported by lkp, if NUMA=n we see a build error:
arch/powerpc/platforms/pseries/hotplug-cpu.c: In function
'pseries_cpu_hotplug_init':
arch/powerpc/platfor
On Mon, 16 Aug 2021 14:10:32 +1000, Michael Ellerman wrote:
> As reported by lkp, if NUMA=n we see a build error:
>
>arch/powerpc/platforms/pseries/hotplug-cpu.c: In function
> 'pseries_cpu_hotplug_init':
>arch/powerpc/platforms/pseries/ho
As reported by lkp, if NUMA=n we see a build error:
arch/powerpc/platforms/pseries/hotplug-cpu.c: In function
'pseries_cpu_hotplug_init':
arch/powerpc/platforms/pseries/hotplug-cpu.c:1022:8: error:
'node_to_cpumask_map' undeclared
1022 |node_to_cpum
From: "Aneesh Kumar K.V"
[ Upstream commit 07d8ad6fd8a3d47f50595ca4826f41dbf4f3a0c6 ]
Update _tlbiel_pid() such that we can avoid build errors like below when
using this function in other places.
arch/powerpc/mm/book3s64/radix_tlb.c: In function
‘__radix__flush_tlb_range_psize’:
arch/powerpc/m
From: "Aneesh Kumar K.V"
[ Upstream commit 07d8ad6fd8a3d47f50595ca4826f41dbf4f3a0c6 ]
Update _tlbiel_pid() such that we can avoid build errors like below when
using this function in other places.
arch/powerpc/mm/book3s64/radix_tlb.c: In function
‘__radix__flush_tlb_range_psize’:
arch/powerpc/m
kefile.build:271:
> arch/powerpc/mm/book3s64/radix_tlb.o] Error 1
> m
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/mm/book3s64: Fix possible build error
https://git.kernel.org/powerpc/c/07d8ad6fd8a3d47f50595ca4826f41dbf4f3a0c6
cheers
Update _tlbiel_pid() such that we can avoid build errors like below when
using this function in other places.
arch/powerpc/mm/book3s64/radix_tlb.c: In function
‘__radix__flush_tlb_range_psize’:
arch/powerpc/mm/book3s64/radix_tlb.c:114:2: warning: ‘asm’ operand 3 probably
does not match constrain
Update _tlbiel_pid() such that we can avoid build errors like below when
using this function in other places.
arch/powerpc/mm/book3s64/radix_tlb.c: In function
‘__radix__flush_tlb_range_psize’:
arch/powerpc/mm/book3s64/radix_tlb.c:114:2: warning: ‘asm’ operand 3 probably
does not match constrain
Update _tlbiel_pid() such that we can avoid build errors like below when
using this function in other places.
arch/powerpc/mm/book3s64/radix_tlb.c: In function
‘__radix__flush_tlb_range_psize’:
arch/powerpc/mm/book3s64/radix_tlb.c:114:2: warning: ‘asm’ operand 3 probably
does not match constrain
| ^~~~
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/kvm: Fix build error when PPC_MEM_KEYS/PPC_PSERIES=n
https://git.kernel.org/powerpc/c/ee1bc694fbaec1a662770703fc34a74abf418938
cheers
lkp reported a randconfig failure:
In file included from arch/powerpc/include/asm/book3s/64/pkeys.h:6,
from arch/powerpc/kvm/book3s_64_mmu_host.c:15:
arch/powerpc/include/asm/book3s/64/hash-pkey.h: In function
'hash__vmflag_to_pte_pkey_bits':
>> arch/powerpc/includ
Update _tlbiel_pid() such that we can avoid build errors like below when
using this function in other places.
arch/powerpc/mm/book3s64/radix_tlb.c: In function
‘__radix__flush_tlb_range_psize’:
arch/powerpc/mm/book3s64/radix_tlb.c:114:2: warning: ‘asm’ operand 3 probably
does not match constrain
"Aneesh Kumar K.V" writes:
> Update _tlbiel_pid() such that we can avoid build errors like below when
> using this function in other places.
>
> arch/powerpc/mm/book3s64/radix_tlb.c: In function
> ‘__radix__flush_tlb_range_psize’:
> arch/powerpc/mm/book3s64/radix_tlb.c:114:2: warning: ‘asm’ opera
When I changed the rc variable to be long rather than int64_t I
neglected to update the printk(), leading to a build break:
arch/powerpc/platforms/pseries/papr_scm.c: In function 'papr_scm_pmem_flush':
arch/powerpc/platforms/pseries/papr_scm.c:144:26: warning: format
'%lld' expects argumen
Update _tlbiel_pid() such that we can avoid build errors like below when
using this function in other places.
arch/powerpc/mm/book3s64/radix_tlb.c: In function
‘__radix__flush_tlb_range_psize’:
arch/powerpc/mm/book3s64/radix_tlb.c:114:2: warning: ‘asm’ operand 3 probably
does not match constrain
Le 30/03/2021 à 08:07, Aneesh Kumar K.V a écrit :
Update _tlbiel_pid() such that we can avoid build errors like below when
using this function in other places.
arch/powerpc/mm/book3s64/radix_tlb.c: In function
‘__radix__flush_tlb_range_psize’:
arch/powerpc/mm/book3s64/radix_tlb.c:114:2: warn
Update _tlbiel_pid() such that we can avoid build errors like below when
using this function in other places.
arch/powerpc/mm/book3s64/radix_tlb.c: In function
‘__radix__flush_tlb_range_psize’:
arch/powerpc/mm/book3s64/radix_tlb.c:114:2: warning: ‘asm’ operand 3 probably
does not match constrain
t; exception prolog stack check to fix build error") for kernel 5.10
> > >
> > > It fixes the build failure on v5.10 reported by kernel test robot
> > > and by David Michael.
> > >
> > > This fix is not in Linux tree yet, it is in next br
Le 15/02/2021 à 15:30, Greg KH a écrit :
On Fri, Feb 12, 2021 at 08:57:14AM +, Christophe Leroy wrote:
This is backport of 3642eb21256a ("powerpc/32: Preserve cr1 in
exception prolog stack check to fix build error") for kernel 5.10
It fixes the build failure on v5.10 reported
On Fri, Feb 12, 2021 at 08:57:14AM +, Christophe Leroy wrote:
> This is backport of 3642eb21256a ("powerpc/32: Preserve cr1 in
> exception prolog stack check to fix build error") for kernel 5.10
>
> It fixes the build failure on v5.10 reported by kernel test robot
This is backport of 3642eb21256a ("powerpc/32: Preserve cr1 in
exception prolog stack check to fix build error") for kernel 5.10
It fixes the build failure on v5.10 reported by kernel test robot
and by David Michael.
This fix is not in Linux tree yet, it is in next branch in po
_phbs = mpc83xx_setup_pci,
>| ^
>| mpc83xx_setup_arch
>
> [...]
Applied to powerpc/next.
[1/3] powerpc/83xx: Fix build error when CONFIG_PCI=n
https://git.kernel.org/powerpc/c/5c47c44f157f408c862b144bbd1d1e161a521aa2
[2/3] powerpc/mm/64s: Fix no p
o CR when we check stack overflow.
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/32: Preserve cr1 in exception prolog stack check to fix build
error
https://git.kernel.org/powerpc/c/3642eb21256a317ac14e9ed560242c6d20cf06d9
cheers
As reported by lkp:
arch/powerpc/platforms/83xx/km83xx.c:183:19: error: 'mpc83xx_setup_pci'
undeclared here (not in a function)
183 | .discover_phbs = mpc83xx_setup_pci,
| ^
| mpc83xx_setup_arch
There is a stub defined
THREAD_ALIGN_SHIFT = THREAD_SHIFT + 1 = PAGE_SHIFT + 1
Maximum PAGE_SHIFT is 18 for 256k pages so
THREAD_ALIGN_SHIFT is 19 at the maximum.
No need to clobber cr1, it can be preserved when moving r1
into CR when we check stack overflow.
This reduces the number of instructions in Machine Check Exce
THREAD_ALIGN_SHIFT = THREAD_SHIFT + 1 = PAGE_SHIFT + 1
Maximum PAGE_SHIFT is 18 for 256k pages so
THREAD_ALIGN_SHIFT is 19 at the maximum.
No need to clobber cr1, it can be preserved when moving r1
into CR when we check stack overflow.
This reduces the number of instructions in Machine Check Exce
On Wed, 20 Jan 2021 14:28:38 +0100, Michal Suchanek wrote:
> ./arch/powerpc/include/asm/paravirt.h:83:44: error: implicit declaration
> of function 'smp_processor_id'; did you mean 'raw_smp_processor_id'?
>
> smp_processor_id is defined in linux/smp.h but it is no
./arch/powerpc/include/asm/paravirt.h:83:44: error: implicit declaration
of function 'smp_processor_id'; did you mean 'raw_smp_processor_id'?
smp_processor_id is defined in linux/smp.h but it is not included.
The build error happens only when the patch is applied to 5.3 kern
powerpc/fixes.
[1/1] powerpc/pkeys: Fix build error with PPC_MEM_KEYS disabled
https://git.kernel.org/powerpc/c/1e4e4bcaf70ec89f8b499c93a83d078c1e5c0ea6
cheers
IS_ENABLED() instead of #ifdef still requires variable declaration.
In this specific case, default_uamor is declared in asm/pkeys.h which
is only included if PPC_MEM_KEYS is enabled.
arch/powerpc/mm/book3s64/hash_utils.c: In function
‘hash__early_init_mmu_secondary’:
arch/powerpc/mm/book3s64/hash
ifdef where it's used.
Applied to powerpc/next.
[1/1] powerpc/fadump: Fix build error with CONFIG_PRESERVE_FA_DUMP=y
https://git.kernel.org/powerpc/c/5f987caec521cbb00d4ba2dc641ac8074626b762
cheers
On 7/27/20 4:03 AM, Michael Ellerman wrote:
skiroot_defconfig fails:
arch/powerpc/kernel/fadump.c:48:17: error: ‘cpus_in_fadump’ defined but not used
48 | static atomic_t cpus_in_fadump;
Fix it by moving the definition into the #ifdef where it's used.
Fixes: ba608c4fa12c ("powerpc/fadump:
u_has_feature'
> 113 | if (!cpu_has_feature(CPU_FTR_ARCH_31)) {
> | ^~~
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/test_emulate_sstep: Fix build error
https://git.kernel.org/powerpc/c/70cc062c47e7851335ff4c44ba9b362174baf7d4
cheers
skiroot_defconfig fails:
arch/powerpc/kernel/fadump.c:48:17: error: ‘cpus_in_fadump’ defined but not used
48 | static atomic_t cpus_in_fadump;
Fix it by moving the definition into the #ifdef where it's used.
Fixes: ba608c4fa12c ("powerpc/fadump: fix race between pstore write and fadump
crash
ppc64_book3e_allmodconfig fails with:
arch/powerpc/lib/test_emulate_step.c: In function 'test_pld':
arch/powerpc/lib/test_emulate_step.c:113:7: error: implicit declaration of
function 'cpu_has_feature'
113 | if (!cpu_has_feature(CPU_FTR_ARCH_31)) {
| ^~~
Add an
From: Peter Zijlstra
Date: Tue, 23 Jun 2020 10:36:48 +0200
> In order to break a header dependency between lockdep and task_struct,
> I need per-cpu stuff from lockdep.
>
> Signed-off-by: Peter Zijlstra (Intel)
Acked-by: David S. Miller
In order to break a header dependency between lockdep and task_struct,
I need per-cpu stuff from lockdep.
Signed-off-by: Peter Zijlstra (Intel)
---
arch/sparc/include/asm/percpu_64.h |2 ++
arch/sparc/include/asm/trap_block.h |2 ++
2 files changed, 4 insertions(+)
--- a/arch/sparc/inc
On Thu, Jun 04, 2020 at 06:57:03PM +0200, Peter Zijlstra wrote:
> I think I see, what happens is that these headers end up in the VDSO
> build, and that doesn't have these CFLAGS, because userspace.
>
> Let me see what to do about that.
I feel like the below is cheating, but it's the best I coul
On Fri, May 29, 2020 at 04:29:17PM -0700, David Miller wrote:
> From: Peter Zijlstra
> Date: Fri, 29 May 2020 23:35:51 +0200
>
> > ../arch/sparc/include/asm/percpu_64.h:7:24: warning: call-clobbered
> > register used for global register variable
> > register unsigned long __local_per_cpu_offset
From: Peter Zijlstra
Date: Fri, 29 May 2020 23:35:51 +0200
> ../arch/sparc/include/asm/percpu_64.h:7:24: warning: call-clobbered register
> used for global register variable
> register unsigned long __local_per_cpu_offset asm("g5");
The "-ffixed-g5" option on the command line tells gcc that we
In order to break a header dependency between lockdep and task_struct,
I need per-cpu stuff from lockdep.
Including from lockdep.h gives a build error, this
patch cures that, but results in the following warning:
../arch/sparc/include/asm/percpu_64.h:7:24: warning: call-clobbered register
used
Hi Abdul,
On Thu, 22 Aug 2019 11:16:51 +0530 Abdul Haleem
wrote:
>
> Today's linux-next kernel 5.3.0-rc5-next-20190820 failed to build on my
> powerpc machine
>
> Build errors:
> drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c: In function amdgpu_exit:
> drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c:1471:2:
Greeting's
Today's linux-next kernel 5.3.0-rc5-next-20190820 failed to build on my
powerpc machine
Build errors:
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c: In function amdgpu_exit:
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c:1471:2: error: implicit
declaration of function mmu_notifier_synchronize
[-Wer
Greeting's
Today's linux-next kernel 5.3.0-rc5-next-20190820 failed to build on my
powerpc machine
Build errors:
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c: In function amdgpu_exit:
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c:1471:2: error: implicit
declaration of function mmu_notifier_synchronize
[-Wer
On Tue, Jul 09, 2019 at 09:56:37PM +0530, Abdul Haleem wrote:
> Greeting's
>
> linux-next failed to build on Power 9 Box with below error
>
> In file included from drivers/gpu/drm/amd/amdgpu/amdgpu.h:72:0,
> from drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c:39:
> drivers/gpu/drm/amd/a
https://bugzilla.kernel.org/show_bug.cgi?id=203725
Bug ID: 203725
Summary: Build error: 'init_module' specifies less restrictive
attribute than its target 'rtas_flash_init': 'cold'
Product: Platform Specific/Ha
https://bugzilla.kernel.org/show_bug.cgi?id=203723
Bug ID: 203723
Summary: Build error: taking address of packed member of
'struct ftrace_graph_ent' may result in an unaligned
pointer value
Product: Platfor
https://bugzilla.kernel.org/show_bug.cgi?id=203609
Michael Ellerman (mich...@ellerman.id.au) changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
https://bugzilla.kernel.org/show_bug.cgi?id=203609
Michael Ellerman (mich...@ellerman.id.au) changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://bugzilla.kernel.org/show_bug.cgi?id=203609
Bug ID: 203609
Summary: Build error: implicit declaration of function
'cpu_mitigations_off'
Product: Platform Specific/Hardware
Version: 2.5
Kernel Version: 4.19.43 an
https://bugzilla.kernel.org/show_bug.cgi?id=203161
Michael Ellerman (mich...@ellerman.id.au) changed:
What|Removed |Added
Status|RESOLVED|CLOSED
On Wed, 2019-04-03 at 06:05:14 UTC, "Aneesh Kumar K.V" wrote:
> The current value of MAX_PHYSMEM_BITS cannot work with 32 bit configs.
> We used to have MAX_PHYSMEM_BITS not defined without SPARSEMEM and 32
> bit configs never expected a value to be set for MAX_PHYSMEM_BITS.
>
> Dependent code suc
The current value of MAX_PHYSMEM_BITS cannot work with 32 bit configs.
We used to have MAX_PHYSMEM_BITS not defined without SPARSEMEM and 32
bit configs never expected a value to be set for MAX_PHYSMEM_BITS.
Dependent code such as zsmalloc derived the right values based on other
fields. Instead of
On Tue, 2019-01-01 at 03:55:13 UTC, Michael Ellerman wrote:
> Old GCCs (4.6.3 at least), aren't able to follow the logic in
> __kvmhv_copy_tofrom_guest_radix() and warn that old_pid is used
> uninitialized:
>
> arch/powerpc/kvm/book3s_64_mmu_radix.c:75:3: error: 'old_pid' may be
> used uniniti
Old GCCs (4.6.3 at least), aren't able to follow the logic in
__kvmhv_copy_tofrom_guest_radix() and warn that old_pid is used
uninitialized:
arch/powerpc/kvm/book3s_64_mmu_radix.c:75:3: error: 'old_pid' may be
used uninitialized in this function
The logic is OK, we only use old_pid if quadran
On Mon, Oct 29, 2018 at 11:43 PM Abdul Haleem
wrote:
>
> Greeting's
>
> mainline build fails on my powerpc with commit 55469b : drivers: net:
> remove inclusion when not needed
>
> Machine type: PowerPC power 8 bare-metal
> kernel : 4.19.0
> gcc : 4.8.5
> config attached
>
Thanks for the report
Greeting's
mainline build fails on my powerpc with commit 55469b : drivers: net:
remove inclusion when not needed
Machine type: PowerPC power 8 bare-metal
kernel : 4.19.0
gcc : 4.8.5
config attached
build errors:
drivers/net/ethernet/mellanox/mlx4/en_rx.c:582:18: warning: ‘struct
iphdr’ declar
On Tue, Oct 9, 2018 at 5:40 AM Abdul Haleem wrote:
>
> On Tue, 2018-10-09 at 20:47 +1100, Michael Ellerman wrote:
> > Abdul Haleem writes:
> > > Greeting's
> > >
> > > Today's linux-next fails to build on ppc with below error
> > >
> > > drivers/pci/pcie/aer_inject.c: In function ‘aer_inject_ftra
On Tue, 2018-10-09 at 20:47 +1100, Michael Ellerman wrote:
> Abdul Haleem writes:
> > Greeting's
> >
> > Today's linux-next fails to build on ppc with below error
> >
> > drivers/pci/pcie/aer_inject.c: In function ‘aer_inject_ftrace_thunk’:
> > drivers/pci/pcie/aer_inject.c:444:6: error: ‘struct p
Abdul Haleem writes:
> Greeting's
>
> Today's linux-next fails to build on ppc with below error
>
> drivers/pci/pcie/aer_inject.c: In function ‘aer_inject_ftrace_thunk’:
> drivers/pci/pcie/aer_inject.c:444:6: error: ‘struct pt_regs’ has no
> member named ‘ip’
> regs->ip = (unsigned long) hook->f
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Randy Dunlap
[ Upstream commit c133459765fae249ba482f62e12f987aec4376f0 ]
CC [M] drivers/net/ethernet/freescale/fman/fman.o
In file included from ../drivers/net/ethernet/freescale/fman/fman
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Randy Dunlap
[ Upstream commit c133459765fae249ba482f62e12f987aec4376f0 ]
CC [M] drivers/net/ethernet/freescale/fman/fman.o
In file included from ../drivers/net/ethernet/freescale/fman/fman
1 - 100 of 326 matches
Mail list logo
