From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Matthew Helsley <mhelsley@vmware.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
David Woodhouse <dwmw2@infradead.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Jason Baron <jbaron@akamai.com>, Jiri Kosina <jkosina@suse.cz>
Subject: Re: [POC][RFC][PATCH 1/2] jump_function: Addition of new feature "jump_function"
Date: Fri, 5 Oct 2018 22:02:20 -0400 [thread overview]
Message-ID: <20181005220220.770d9e18@vmware.local.home> (raw)
In-Reply-To: <20181006015720.634688468@goodmis.org>
On Fri, 05 Oct 2018 21:51:11 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> +#define arch_dynfunc_trampoline(name, def) \
> + asm volatile ( \
> + ".globl dynfunc_" #name "; \n\t" \
> + "dynfunc_" #name ": \n\t" \
> + "jmp " #def " \n\t" \
> + ".balign 8 \n \t" \
> + : : : "memory" )
> +
Note, the assembler can easily put in a two byte jump here. The .balign
was suppose to also have some padding (nop) incase that happens. It's
fine, because we can just replace it with a 5 byte jump, as long as we
have 3 bytes afterward if it is a two byte jump.
-- Steve
next prev parent reply other threads:[~2018-10-06 2:02 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-06 1:51 [POC][RFC][PATCH 0/2] PROOF OF CONCEPT: Dynamic Functions (jump functions) Steven Rostedt
2018-10-06 1:51 ` [POC][RFC][PATCH 1/2] jump_function: Addition of new feature "jump_function" Steven Rostedt
2018-10-06 2:00 ` Steven Rostedt
2018-10-06 2:02 ` Steven Rostedt [this message]
2018-10-06 2:03 ` Steven Rostedt
2018-10-06 15:15 ` Steven Rostedt
2018-10-06 12:12 ` Peter Zijlstra
2018-10-06 13:39 ` Steven Rostedt
2018-10-06 15:13 ` Andy Lutomirski
2018-10-06 15:16 ` Steven Rostedt
2018-10-08 7:21 ` Peter Zijlstra
2018-10-08 8:33 ` Andy Lutomirski
2018-10-08 15:57 ` Peter Zijlstra
2018-10-08 16:29 ` Andy Lutomirski
2018-10-08 16:39 ` Steven Rostedt
2018-10-08 16:39 ` Peter Zijlstra
2018-10-08 17:25 ` Andy Lutomirski
2018-10-08 17:30 ` Ard Biesheuvel
2018-10-08 17:42 ` Andy Lutomirski
2018-10-08 17:44 ` Jiri Kosina
2018-10-08 17:45 ` Ard Biesheuvel
2018-10-08 17:47 ` Andy Lutomirski
2018-10-09 2:17 ` Josh Poimboeuf
2018-10-09 3:57 ` Steven Rostedt
2018-10-10 17:52 ` Josh Poimboeuf
2018-10-10 18:03 ` Andy Lutomirski
2018-10-10 18:16 ` Josh Poimboeuf
2018-10-10 18:17 ` Josh Poimboeuf
2018-10-10 21:13 ` Andy Lutomirski
2018-10-11 3:07 ` Josh Poimboeuf
2018-10-11 12:52 ` Josh Poimboeuf
2018-10-11 16:20 ` Andy Lutomirski
2018-10-10 18:33 ` Josh Poimboeuf
2018-10-10 18:56 ` Steven Rostedt
2018-10-10 20:16 ` Josh Poimboeuf
2018-10-10 20:57 ` Andy Lutomirski
2018-10-08 16:31 ` Steven Rostedt
2018-10-08 11:30 ` Ard Biesheuvel
2018-10-09 3:44 ` Masami Hiramatsu
2018-10-09 3:55 ` Steven Rostedt
2018-10-09 16:04 ` Masami Hiramatsu
2018-10-09 8:59 ` David Laight
2018-10-06 1:51 ` [POC][RFC][PATCH 2/2] tracepoints: Implement it with dynamic functions Steven Rostedt
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=20181005220220.770d9e18@vmware.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=dwmw2@infradead.org \
--cc=jbaron@akamai.com \
--cc=jkosina@suse.cz \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhelsley@vmware.com \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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).