From: Suraj Jitindar Singh <sjitindarsingh@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, live-patching@vger.kernel.org,
catalin.marinas@arm.com, will@kernel.org, mark.rutland@arm.com,
madvenka@linux.microsoft.com, duwe@lst.de,
benh@kernel.crashing.org
Subject: Re: [RFC PATCH 1/1] arm64: implement live patching
Date: Tue, 08 Jun 2021 17:12:15 -0700 [thread overview]
Message-ID: <1a6306bb029779e26d92ba3e2608e500ce47c6f7.camel@gmail.com> (raw)
In-Reply-To: <20210607170154.GC10625@sirena.org.uk>
On Mon, 2021-06-07 at 18:01 +0100, Mark Brown wrote:
> On Fri, Jun 04, 2021 at 04:59:30PM -0700, Suraj Jitindar Singh wrote:
>
> > + * CONFIG_ARM64_BTI_KERNEL:
> > + * - Inserts a hint #0x22 on function entry if the function is
> > called
> > + * indirectly (to satisfy BTI requirements), which is inserted
> > before
> > + * the two nops from above.
>
> Please write out the symbolic name of the HINT (BTI C here) rather
> than
> the number, it helps with readability especially in a case like this
> where there are multiple relevant hints.
Thanks for taking a look, I will keep that in mind for when I resend.
next prev parent reply other threads:[~2021-06-09 0:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 23:59 [RFC PATCH 1/1] arm64: implement live patching Suraj Jitindar Singh
2021-06-07 10:20 ` Mark Rutland
2021-06-07 13:08 ` Joe Lawrence
2021-06-09 0:32 ` Suraj Jitindar Singh
2021-06-09 23:57 ` Suraj Jitindar Singh
2021-06-07 17:01 ` Mark Brown
2021-06-09 0:12 ` Suraj Jitindar Singh [this message]
2021-06-17 9:29 ` nobuta.keiya
2021-06-17 18:32 ` Madhavan T. Venkataraman
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=1a6306bb029779e26d92ba3e2608e500ce47c6f7.camel@gmail.com \
--to=sjitindarsingh@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=duwe@lst.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=madvenka@linux.microsoft.com \
--cc=mark.rutland@arm.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;
as well as URLs for NNTP newsgroup(s).