From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@ozlabs.org
Subject: Re: [1/5] powerpc/asm: Add a patch_site macro & helpers for patching instructions
Date: Thu, 9 Aug 2018 00:25:43 +1000 (AEST) [thread overview]
Message-ID: <41ltw948whz9s4V@ozlabs.org> (raw)
In-Reply-To: <20180723150756.11108-1-mpe@ellerman.id.au>
On Mon, 2018-07-23 at 15:07:52 UTC, Michael Ellerman wrote:
> Add a macro and some helper C functions for patching single asm
> instructions.
>
> The gas macro means we can do something like:
>
> 1: nop
> patch_site 1b, patch__foo
>
> Which is less visually distracting than defining a GLOBAL symbol at 1,
> and also doesn't pollute the symbol table which can confuse eg. perf.
>
> These are obviously similar to our existing feature sections, but are
> not automatically patched based on CPU/MMU features, rather they are
> designed to be manually patched by C code at some arbitrary point.
>
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Series applied to powerpc next.
https://git.kernel.org/powerpc/c/06d0bbc6d0f56dacac3a79900e9a9a
cheers
next prev parent reply other threads:[~2018-08-08 14:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 15:07 [PATCH 1/5] powerpc/asm: Add a patch_site macro & helpers for patching instructions Michael Ellerman
2018-07-23 15:07 ` [PATCH 2/5] powerpc/64s: Add new security feature flags for count cache flush Michael Ellerman
2018-07-23 15:07 ` [PATCH 3/5] powerpc/64s: Add support for software " Michael Ellerman
2018-07-23 15:07 ` [PATCH 4/5] powerpc/pseries: Query hypervisor for count cache flush settings Michael Ellerman
2018-07-23 15:07 ` [PATCH 5/5] powerpc/powernv: Query firmware " Michael Ellerman
2018-08-08 14:25 ` Michael Ellerman [this message]
2018-08-08 16:30 ` [PATCH 1/5] powerpc/asm: Add a patch_site macro & helpers for patching instructions Christophe LEROY
2018-08-09 6:56 ` Christophe LEROY
2018-08-09 9:52 ` 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=41ltw948whz9s4V@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
/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.