From: Peter Zijlstra <peterz@infradead.org>
To: Daniel Bristot de Oliveira <bristot@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
"Steven Rostedt (VMware)" <rostedt@goodmis.org>,
Jiri Kosina <jkosina@suse.cz>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Chris von Recklinghausen <crecklin@redhat.com>,
Jason Baron <jbaron@akamai.com>, Scott Wood <swood@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Clark Williams <williams@redhat.com>,
x86@kernel.org
Subject: Re: [PATCH V5 5/7] x86/alternative: Batch of patch operations
Date: Mon, 15 Apr 2019 13:35:35 +0200 [thread overview]
Message-ID: <20190415113535.GK11158@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <a4e6c503c552f7c02273c5f000c2c601a1b87c32.1554106794.git.bristot@redhat.com>
On Mon, Apr 01, 2019 at 10:58:17AM +0200, Daniel Bristot de Oliveira wrote:
> + ip = (void *) regs->ip - sizeof(unsigned char);
That one confused me mightily. Does that want to be:
ip = (void *)regs->ip - LEN_INT3;
or something? Even just a naked 1 would've been less confusing.
>
> + /*
> + * Skip the binary search if there is a single member in the vector.
> + */
> + if (unlikely(bp_patching.nr_entries == 1))
> + goto single_poke;
> +
> + tp = bsearch(ip, bp_patching.vec, bp_patching.nr_entries,
> + sizeof(struct text_patch_loc),
> + patch_cmp);
> + if (!tp)
> + return 0;
> +
> + /* set up the specified breakpoint detour */
> + regs->ip = (unsigned long) tp->detour;
> return 1;
> +single_poke:
> + if (ip == bp_patching.vec->addr) {
> + regs->ip = (unsigned long) bp_patching.vec->detour;
> + return 1;
> + }
> +
> + return 0;
if (bp_patching.nr_entries > 1) {
tp = bsearch(ip, bp_patching.vec, bp_patching.nr_entries,
sizeof(struct text_patch_loc), patch_cmp);
if (!tp)
return 0;
} else {
tp = bp_patching.vec;
if (tp->addr != ip)
return 0;
}
regs->ip = (unsigned long)tp->detour;
return 1;
> }
> NOKPROBE_SYMBOL(poke_int3_handler);
> +void text_poke_bp_batch(struct text_patch_loc *tp, unsigned int nr_entries)
> {
> + int patched_all_but_first = 0;
> unsigned char int3 = 0xcc;
> + unsigned int i;
>
> lockdep_assert_held(&text_mutex);
>
> + bp_patching.vec = tp;
> + bp_patching.nr_entries = nr_entries;
> + bp_patching.in_progress = true;
> /*
> * Corresponding read barrier in int3 notifier for making sure the
> * in_progress and handler are correctly ordered wrt. patching.
> */
> smp_wmb();
>
> + /*
> + * First step: add a int3 trap to the address that will be patched.
> + */
> + for (i = 0; i < nr_entries; i++)
> + text_poke(tp[i].addr, &int3, sizeof(int3));
>
> on_each_cpu(do_sync_core, NULL, 1);
>
> + /*
> + * Second step: update all but the first byte of the patched range.
> + */
> + for (i = 0; i < nr_entries; i++) {
> + if (tp[i].len - sizeof(int3) > 0) {
> + text_poke((char *)tp[i].addr + sizeof(int3),
> + (const char *)tp[i].opcode + sizeof(int3),
> + tp[i].len - sizeof(int3));
> + patched_all_but_first++;
> + }
> + }
> +
> + if (patched_all_but_first) {
> /*
> * According to Intel, this core syncing is very likely
> * not necessary and we'd be safe even without it. But
> @@ -821,15 +874,52 @@ void *text_poke_bp(void *addr, const void *opcode, size_t len, void *handler)
> on_each_cpu(do_sync_core, NULL, 1);
> }
>
> + /*
> + * Third step: replace the first byte (int3) by the first byte of
> + * replacing opcode.
> + */
> + for (i = 0; i < nr_entries; i++)
> + text_poke(tp[i].addr, tp[i].opcode, sizeof(int3));
>
> on_each_cpu(do_sync_core, NULL, 1);
> /*
> * sync_core() implies an smp_mb() and orders this store against
> * the writing of the new instruction.
> */
> + bp_patching.vec = NULL;
> + bp_patching.nr_entries = 0;
> + bp_patching.in_progress = false;
> +}
next prev parent reply other threads:[~2019-04-15 11:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 8:58 [PATCH V5 0/7] x86/jump_label: Bound IPIs sent when updating a static key Daniel Bristot de Oliveira
2019-04-01 8:58 ` [PATCH V5 1/7] jump_label: Add for_each_label_entry helper Daniel Bristot de Oliveira
2019-04-15 10:51 ` Peter Zijlstra
2019-04-15 11:29 ` Daniel Bristot de Oliveira
2019-04-01 8:58 ` [PATCH V5 2/7] jump_label: Add a jump_label_can_update() helper Daniel Bristot de Oliveira
2019-04-01 8:58 ` [PATCH V5 3/7] x86/jump_label: Add a __jump_label_set_jump_code() helper Daniel Bristot de Oliveira
2019-04-01 8:58 ` [PATCH V5 4/7] jump_label: Sort entries of the same key by the code Daniel Bristot de Oliveira
2019-04-15 10:55 ` Peter Zijlstra
2019-04-15 11:33 ` Daniel Bristot de Oliveira
2019-04-01 8:58 ` [PATCH V5 5/7] x86/alternative: Batch of patch operations Daniel Bristot de Oliveira
2019-04-15 11:35 ` Peter Zijlstra [this message]
2019-04-01 8:58 ` [PATCH V5 6/7] jump_label: Batch updates if arch supports it Daniel Bristot de Oliveira
2019-04-15 11:50 ` Peter Zijlstra
2019-04-01 8:58 ` [PATCH V5 7/7] x86/jump_label: Batch jump label updates Daniel Bristot de Oliveira
2019-04-15 11:54 ` Peter Zijlstra
2019-04-15 12:15 ` Daniel Bristot de Oliveira
2019-05-02 20:18 ` Daniel Bristot de Oliveira
2019-04-15 9:52 ` [PATCH V5 0/7] x86/jump_label: Bound IPIs sent when updating a static key Daniel Bristot de Oliveira
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=20190415113535.GK11158@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=bristot@redhat.com \
--cc=crecklin@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=jbaron@akamai.com \
--cc=jkosina@suse.cz \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=mtosatti@redhat.com \
--cc=rostedt@goodmis.org \
--cc=swood@redhat.com \
--cc=tglx@linutronix.de \
--cc=williams@redhat.com \
--cc=x86@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).