All of lore.kernel.org
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64: updates for 4.19
Date: Thu, 16 Aug 2018 10:14:54 +0100	[thread overview]
Message-ID: <20180816091454.GA31093@arm.com> (raw)
In-Reply-To: <CALAqxLVeSHp+D=9t0f7ve7YgSzqVNTkVVzv-8tdQkJARJ8Bo8Q@mail.gmail.com>

Hi John,

On Wed, Aug 15, 2018 at 04:55:15PM -0700, John Stultz wrote:
> On Tue, Aug 14, 2018 at 4:36 AM, Will Deacon <will.deacon@arm.com> wrote:
> >
> > Please pull these arm64 updates for 4.19. Details in the tag, but please be
> > aware that we've pulled in the x86/mm branch from -tip so that we can make
> > use of the core ioremap changes which allow us to put down huge mappings
> > in the vmalloc area without screwing up the TLB. Much of the positive
> > diffstat is because of the rseq selftest for arm64.
> >
> > There is a trivial conflict in arch/arm64/Makefile with your tree, since
> > we effectively rewrote a fix that was merged in -rc5 [96f95a17c1cf]. The
> > correct resolution is therefore to prefer the code using ld-option, which
> > is what we have here. We also ran into a couple of trivial conflicts that
> > were resolved in -next with the KVM and EFI trees.
> >
> 
> Hey Will,
>   So I noticed issues booting Linus' master on the HiKey960 board I
> have today (something hangs early in boot before I get any serial
> output), and isolated the issue down to your branch here.
> 
> It seems to be coming from 693350a79980 ("arm64: insn: Don't fallback
> on nosync path for general insn patching"), and reverting that change
> resolves the issue for me.
> 
> If you have any suggestions for alternative fixes or things to try,
> please let me know.

Hmm, sorry about that. It's also just been reported on linux-arm-kernel[1], and
they have a backtrace, so I'll take a look today.

Cheers,

Will

[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2018-August/596961.html

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: John Stultz <john.stultz@linaro.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Marc Zyngier <marc.zyngier@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Amit Pundir <amit.pundir@linaro.org>,
	Vishal Bhoj <vishal.bhoj@linaro.org>
Subject: Re: [GIT PULL] arm64: updates for 4.19
Date: Thu, 16 Aug 2018 10:14:54 +0100	[thread overview]
Message-ID: <20180816091454.GA31093@arm.com> (raw)
In-Reply-To: <CALAqxLVeSHp+D=9t0f7ve7YgSzqVNTkVVzv-8tdQkJARJ8Bo8Q@mail.gmail.com>

Hi John,

On Wed, Aug 15, 2018 at 04:55:15PM -0700, John Stultz wrote:
> On Tue, Aug 14, 2018 at 4:36 AM, Will Deacon <will.deacon@arm.com> wrote:
> >
> > Please pull these arm64 updates for 4.19. Details in the tag, but please be
> > aware that we've pulled in the x86/mm branch from -tip so that we can make
> > use of the core ioremap changes which allow us to put down huge mappings
> > in the vmalloc area without screwing up the TLB. Much of the positive
> > diffstat is because of the rseq selftest for arm64.
> >
> > There is a trivial conflict in arch/arm64/Makefile with your tree, since
> > we effectively rewrote a fix that was merged in -rc5 [96f95a17c1cf]. The
> > correct resolution is therefore to prefer the code using ld-option, which
> > is what we have here. We also ran into a couple of trivial conflicts that
> > were resolved in -next with the KVM and EFI trees.
> >
> 
> Hey Will,
>   So I noticed issues booting Linus' master on the HiKey960 board I
> have today (something hangs early in boot before I get any serial
> output), and isolated the issue down to your branch here.
> 
> It seems to be coming from 693350a79980 ("arm64: insn: Don't fallback
> on nosync path for general insn patching"), and reverting that change
> resolves the issue for me.
> 
> If you have any suggestions for alternative fixes or things to try,
> please let me know.

Hmm, sorry about that. It's also just been reported on linux-arm-kernel[1], and
they have a backtrace, so I'll take a look today.

Cheers,

Will

[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2018-August/596961.html

  reply	other threads:[~2018-08-16  9:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-14 11:36 [GIT PULL] arm64: updates for 4.19 Will Deacon
2018-08-14 11:36 ` Will Deacon
2018-08-15 23:55 ` John Stultz
2018-08-15 23:55   ` John Stultz
2018-08-16  9:14   ` Will Deacon [this message]
2018-08-16  9:14     ` Will Deacon

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=20180816091454.GA31093@arm.com \
    --to=will.deacon@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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.