From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alexey Kardashevskiy <aik@ozlabs.ru>, linuxppc-dev@lists.ozlabs.org
Cc: Michael Ellerman <mpe@ellerman.id.au>, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH kernel] powerpc/powernv: Fix clobbered MSR
Date: Fri, 03 Mar 2017 08:37:37 +1100 [thread overview]
Message-ID: <1488490657.2870.74.camel@kernel.crashing.org> (raw)
In-Reply-To: <20170302064124.26342-1-aik@ozlabs.ru>
On Thu, 2017-03-02 at 17:41 +1100, Alexey Kardashevskiy wrote:
> With CONFIG_DEBUG_INFO_SPLIT=y, the makefile adds "-gsplit-dwarf" which
> somehow makes the scripts/gcc-goto.sh test fail and not have
> CC_HAVE_ASM_GOTO defined so the alternative OPAL_BRANCH() is used
This needs to be fixed too though. That alternative path has much more
overhead accross the board. Losing "asm goto" because of a broken test
is nasty.
Cheers,
Ben.
next prev parent reply other threads:[~2017-03-02 21:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 6:41 [PATCH kernel] powerpc/powernv: Fix clobbered MSR Alexey Kardashevskiy
2017-03-02 21:37 ` Benjamin Herrenschmidt [this message]
2017-03-03 0:54 ` Alexey Kardashevskiy
2017-03-08 7:25 ` [kernel] " 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=1488490657.2870.74.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=aik@ozlabs.ru \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
/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.