From: Nicholas Piggin <npiggin@gmail.com>
To: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Stephen Rothwell <sfr@canb.auug.org.au>, mpe <mpe@ellerman.id.au>,
ego <ego@linux.vnet.ibm.com>,
sachinp <sachinp@linux.vnet.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
mahesh@linux.vnet.ibm.com
Subject: Re: [linux-next][bisected 1945bc45] build brakes for PowerPC BE configuration on LPAR
Date: Thu, 4 May 2017 20:41:12 +1000 [thread overview]
Message-ID: <20170504204112.130d7735@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <1493889859.7355.17.camel@abdul.in.ibm.com>
On Thu, 04 May 2017 14:54:19 +0530
Abdul Haleem <abdhalee@linux.vnet.ibm.com> wrote:
> Hi,
>
> linux-next build fails on BE config with next-20170424 onwards
>
> the patch https://lkml.org/lkml/2017/4/20/994 fixes a similar issue
> with kvm guest build failure.
>
> arch/powerpc/kernel/exceptions-64s.S: Assembler messages:
> arch/powerpc/kernel/exceptions-64s.S:395: Error: operand out of range
> (0xffffffffffff8280 is not between 0x0000000000000000 and
> 0x000000000000ffff)
> make[1]: *** [arch/powerpc/kernel/head_64.o] Error 1
>
> Bisection resulted with the below bad commit.
>
> commit 1945bc4549e5cb1f9aa873ec29191aa54dc851d
> Author: Nicholas Piggin <npiggin@gmail.com>
> Date: Wed Apr 19 23:05:47 2017 +1000
>
> powerpc/64s: Fix POWER9 machine check handler from stop state
>
> Reviewed-by: Gautham R. Shenoy <ego@linux.vnet.ibm.com>
> Reviewed-by: Mahesh J Salgaonkar <mahesh@linux.vnet.ibm.com>
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
>
> arch/powerpc/include/asm/reg.h | 1 +
> arch/powerpc/kernel/exceptions-64s.S | 79 ++++++++++++++++++++++++++++++++++++++++++++-----------------------------------
> arch/powerpc/kernel/idle_book3s.S | 25 +++++++++++++++++++++++++
> 3 files changed, 70 insertions(+), 35 deletions(-)
>
> the BE configuration file is attached.
>
Thanks for the report. I wouldn't reproduce it with this config. I
suspect the following patch should fix it, can you test?
powerpc/64s: Fix unnecessary machine check handler relocation branch
Similarly to 2563a70c3b ("powerpc/64s: Remove unnecessary relocation
branch from idle handler"), the machine check handler has a BRANCH_TO
from relocated to relocated code, which is unnecessary.
It has also caused build errors with some toolchains:
arch/powerpc/kernel/exceptions-64s.S: Assembler messages:
arch/powerpc/kernel/exceptions-64s.S:395: Error: operand out of range
(0xffffffffffff8280 is not between 0x0000000000000000 and
0x000000000000ffff)
Fixes: 1945bc4549 ("powerpc/64s: Fix POWER9 machine check handler from stop state")
Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
---
arch/powerpc/kernel/exceptions-64s.S | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/arch/powerpc/kernel/exceptions-64s.S b/arch/powerpc/kernel/exceptions-64s.S
index 3840a7700285..ef72065f684c 100644
--- a/arch/powerpc/kernel/exceptions-64s.S
+++ b/arch/powerpc/kernel/exceptions-64s.S
@@ -391,9 +391,7 @@ EXC_COMMON_BEGIN(machine_check_handle_early)
*/
BEGIN_FTR_SECTION
rlwinm. r11,r12,47-31,30,31
- beq- 4f
- BRANCH_TO_COMMON(r10, machine_check_idle_common)
-4:
+ bne machine_check_idle_common
END_FTR_SECTION_IFSET(CPU_FTR_HVMODE | CPU_FTR_ARCH_206)
#endif
--
2.11.0
next prev parent reply other threads:[~2017-05-04 10:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 9:24 [linux-next][bisected 1945bc45] build brakes for PowerPC BE configuration on LPAR Abdul Haleem
2017-05-04 10:29 ` Michael Ellerman
2017-05-04 10:50 ` Abdul Haleem
2017-05-04 10:41 ` Nicholas Piggin [this message]
2017-05-05 4:10 ` Abdul Haleem
2017-05-05 6:40 ` Nicholas Piggin
2017-05-15 5:06 ` [linux-next, bisected, " Michael Ellerman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170504204112.130d7735@roar.ozlabs.ibm.com \
--to=npiggin@gmail.com \
--cc=abdhalee@linux.vnet.ibm.com \
--cc=ego@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=sachinp@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.