All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Miroslav Benes <mbenes@suse.cz>,
	Thomas Gleixner <tglx@linutronix.de>,
	Masami Hiramatsu <mhiramat@kernel.org>
Subject: Re: [PATCH 2/3 v4] ftrace/x86: Allow for arguments to be passed in to ftrace_regs by default
Date: Tue, 10 Nov 2020 10:20:03 +0100	[thread overview]
Message-ID: <20201110092003.GX2594@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20201109181610.1b3f7d9f@oasis.local.home>

On Mon, Nov 09, 2020 at 06:16:10PM -0500, Steven Rostedt wrote:
> ftrace_caller:
> 	[..]
> 	movq $0, CS(%rsp) <- loads zero into pt_regs->cs for internal use only.
> 	[..]

Argh, I missed that. I failed to spot it in the patch. No worries then.

  reply	other threads:[~2020-11-10  9:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-06 21:42 [PATCH 0/3 v4] ftrace: Add access to function arguments for all callbacks Steven Rostedt
2020-11-06 21:42 ` [PATCH 1/3 v4] ftrace: Have the callbacks receive a struct ftrace_regs instead of pt_regs Steven Rostedt
2020-11-07  4:29   ` Masami Hiramatsu
2020-11-06 21:42 ` [PATCH 2/3 v4] ftrace/x86: Allow for arguments to be passed in to ftrace_regs by default Steven Rostedt
2020-11-09 11:10   ` Peter Zijlstra
2020-11-09 23:16     ` Steven Rostedt
2020-11-10  9:20       ` Peter Zijlstra [this message]
2020-11-06 21:42 ` [PATCH 3/3 v4] livepatch: Use the default ftrace_ops instead of REGS when ARGS is available 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=20201110092003.GX2594@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbenes@suse.cz \
    --cc=mhiramat@kernel.org \
    --cc=mingo@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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.