All of lore.kernel.org
 help / color / mirror / Atom feed
From: rostedt@goodmis.org (Steven Rostedt)
Subject: [RFC][PATCH 1/3] x86_64: Add gap to int3 to allow for call emulation
Date: Tue, 7 May 2019 14:57:24 -0400	[thread overview]
Message-ID: <20190507145724.132dc8ec@gandalf.local.home> (raw)
Message-ID: <20190507185724.Tc-54GqMO1-cLx0KlJlpwSzHBNBpxwMPYr1N0FvoUQE@z> (raw)
In-Reply-To: <20190507175655.u3kcvedpfao4rchj@treble>

On Tue, 7 May 2019 12:56:55 -0500
Josh Poimboeuf <jpoimboe@redhat.com> wrote:


> > +	.if \create_gap == 1
> > +	/*
> > +	 * If coming from kernel space, create a 6-word gap to allow the static
> > +	 * call #BP handler to emulate a call instruction.  
> 
> Might as well refer to it as the int3 handler, since that's what the
> rest of the code calls it.  Also, no static calls yet :-)  So:
> 
> s/static call #BP handler/int3 handler/
> 

Done.

-- Steve

  reply	other threads:[~2019-05-07 18:57 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-07 17:42 [RFC][PATCH 0/3] x86_64/ftrace: Emulate calls from int3 when patching functions Steven Rostedt
2019-05-07 17:42 ` Steven Rostedt
2019-05-07 17:42 ` rostedt
2019-05-07 17:42 ` [RFC][PATCH 1/3] x86_64: Add gap to int3 to allow for call emulation Steven Rostedt
2019-05-07 17:42   ` Steven Rostedt
2019-05-07 17:42   ` rostedt
2019-05-07 17:56   ` Josh Poimboeuf
2019-05-07 17:56     ` Josh Poimboeuf
2019-05-07 17:56     ` jpoimboe
2019-05-07 18:57     ` Steven Rostedt [this message]
2019-05-07 18:57       ` Steven Rostedt
2019-05-07 18:57       ` rostedt
2019-05-07 17:42 ` [RFC][PATCH 2/3] x86_64: Allow breakpoints to emulate call functions Steven Rostedt
2019-05-07 17:42   ` Steven Rostedt
2019-05-07 17:42   ` rostedt
2019-05-07 17:53   ` Josh Poimboeuf
2019-05-07 17:53     ` Josh Poimboeuf
2019-05-07 17:53     ` jpoimboe
2019-05-07 19:01     ` Steven Rostedt
2019-05-07 19:01       ` Steven Rostedt
2019-05-07 19:01       ` rostedt
2019-05-07 19:14       ` Josh Poimboeuf
2019-05-07 19:14         ` Josh Poimboeuf
2019-05-07 19:14         ` jpoimboe
2019-05-07 19:20         ` Steven Rostedt
2019-05-07 19:20           ` Steven Rostedt
2019-05-07 19:20           ` rostedt
2019-05-07 19:49           ` Josh Poimboeuf
2019-05-07 19:49             ` Josh Poimboeuf
2019-05-07 19:49             ` jpoimboe
2019-05-07 19:58             ` Steven Rostedt
2019-05-07 19:58               ` Steven Rostedt
2019-05-07 19:58               ` rostedt
2019-05-07 20:02               ` Josh Poimboeuf
2019-05-07 20:02                 ` Josh Poimboeuf
2019-05-07 20:02                 ` jpoimboe
2019-05-07 17:42 ` [RFC][PATCH 3/3] ftrace/x86_64: Emulate call function while updating in breakpoint handler Steven Rostedt
2019-05-07 17:42   ` Steven Rostedt
2019-05-07 17:42   ` 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=20190507145724.132dc8ec@gandalf.local.home \
    --to=rostedt@goodmis.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.