From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Nathan Chancellor <nathan@kernel.org>,
will@kernel.org, ndesaulniers@google.com, trix@redhat.com,
linux-arm-kernel@lists.infradead.org, llvm@lists.linux.dev,
patches@lists.linux.dev
Subject: Re: [PATCH] arm64: Restrict CPU_BIG_ENDIAN to GNU as or LLVM IAS 15.x or newer
Date: Thu, 26 Oct 2023 16:33:15 +0100 [thread overview]
Message-ID: <ZTqGuyj71rnVNPoz@arm.com> (raw)
In-Reply-To: <ZTqGb3MJD6jYZyVR@FVFF77S0Q05N.cambridge.arm.com>
On Thu, Oct 26, 2023 at 04:31:59PM +0100, Mark Rutland wrote:
> On Thu, Oct 26, 2023 at 04:28:45PM +0100, Catalin Marinas wrote:
> > On Wed, Oct 25, 2023 at 11:31:14AM -0700, Nathan Chancellor wrote:
> > > On Wed, Oct 25, 2023 at 07:01:53PM +0100, Mark Rutland wrote:
> > > > On Wed, Oct 25, 2023 at 10:21:28AM -0700, Nathan Chancellor wrote:
> > > > > A recent refactoring in the arm64 tree exposed an assembler bug in LLVM
> > > > > with regards to the generation of NOPs for arm64 big endian, resulting
> > > > > in near-immediate crashes on boot in QEMU.
> > > >
> > > > Could we please put a bit more detail into the commit message about what
> > > > exactly went wrong and how this was detected? I know that can be found
> > > > from the github links below, but having to go chase that is a bit of a
> > > > pain.
> > >
> > > Sure, sorry for leaving that out of the initial revision.
> > >
> > > > Would you be happy with the below? I've also added a Cc stable, since
> > > > this is a potential state corruption issue.
> > >
> > > That text looks much better to me, especially since it explains exactly
> > > what goes wrong here (which I was unsure of, this helps). Thanks a lot!
> > >
> > > Will / Catalin, would you like a v2 with that text or could it just be
> > > copied and pasted from Mark's mail during application time? I am happy
> > > to do whatever.
> >
> > I'll copy/paste Mark's text, no need for v2. Thanks.
>
> If you do, could you fix my typo in the first line? I accidentally wrote:
>
> LLVM's integrated assemble
>
> When that should have been:
>
> LLVM's integrated assembler
>
> If you're already picked the patch it's not worth worrying about.
I can still fix it, hasn't pushed it out yet.
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-10-26 15:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 17:21 [PATCH] arm64: Restrict CPU_BIG_ENDIAN to GNU as or LLVM IAS 15.x or newer Nathan Chancellor
2023-10-25 18:01 ` Mark Rutland
2023-10-25 18:31 ` Nathan Chancellor
2023-10-26 15:28 ` Catalin Marinas
2023-10-26 15:31 ` Mark Rutland
2023-10-26 15:33 ` Catalin Marinas [this message]
2023-10-26 16:36 ` Catalin Marinas
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=ZTqGuyj71rnVNPoz@arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=patches@lists.linux.dev \
--cc=trix@redhat.com \
--cc=will@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox