From: Mark Brown <broonie@kernel.org>
To: Dave Martin <Dave.Martin@arm.com>
Cc: maz@kernel.org, Jean-Philippe Brucker <jean-philippe@linaro.org>,
will@kernel.org, linux-arm-kernel@lists.infradead.org,
catalin.marinas@arm.com
Subject: Re: [PATCH] arm64: Don't insert a BTI instruction at inner labels
Date: Wed, 24 Jun 2020 15:15:35 +0100 [thread overview]
Message-ID: <20200624141535.GG5472@sirena.org.uk> (raw)
In-Reply-To: <20200624134424.GE25945@arm.com>
[-- Attachment #1.1: Type: text/plain, Size: 617 bytes --]
On Wed, Jun 24, 2020 at 02:44:25PM +0100, Dave Martin wrote:
> Since inner labels requiring landing pads are going to be the exception
> rather than the rule, perhaps we can introduce a different macro for
> this. It feels arch-specific to me (indeed, inner labels are kind of
> arch-specific, since they're inevitably in the middle of some asm that
> is unlikely to be handled by core code).
Yes, we'd need a different macro (or argument to it or something).
> Do we know of any code that requires landing pads on inner labels?
There aren't any, that was what Jean-Philippe's analysis in the
changelog covered.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
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:[~2020-06-24 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 11:22 [PATCH] arm64: Don't insert a BTI instruction at inner labels Jean-Philippe Brucker
2020-06-24 13:21 ` Mark Brown
2020-06-24 13:44 ` Dave Martin
2020-06-24 14:15 ` Mark Brown [this message]
2020-06-24 13:54 ` 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=20200624141535.GG5472@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Dave.Martin@arm.com \
--cc=catalin.marinas@arm.com \
--cc=jean-philippe@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--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 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.