public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	Paul Mackerras <paulus@samba.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCHv3] perf x86_64: Fix rsp register for system call fast path
Date: Wed, 3 Oct 2012 14:35:05 +0200	[thread overview]
Message-ID: <20121003123448.GA637@somewhere> (raw)
In-Reply-To: <20121003122947.GB945@krava.brq.redhat.com>

On Wed, Oct 03, 2012 at 02:29:47PM +0200, Jiri Olsa wrote:
> +#ifdef CONFIG_X86_64
> +__weak void

Only annotate with __weak the default implementation you want to be
overriden. Here you want it to actually override the default __weak version.

> +arch_sample_regs_user_fixup(struct perf_regs_user *uregs, int kernel)
> +{
> +	/*
> +	 * If the perf event was triggered within the kernel code
> +	 * path, then it was either syscall or interrupt. While
> +	 * interrupt stores almost all user registers, the syscall
> +	 * fast path does not. At this point we can at least set
> +	 * rsp register right, which is crucial for dwarf unwind.
> +	 *
> +	 * The syscall_get_nr function returns -1 (orig_ax) for
> +	 * interrupt, and positive value for syscall.
> +	 *
> +	 * We have two race windows in here:
> +	 *
> +	 * 1) Few instructions from syscall entry until old_rsp is
> +	 *    set.
> +	 *
> +	 * 2) In syscall/interrupt path from entry until the orig_ax
> +	 *    is set.
> +	 *
> +	 * Above described race windows are fractional opposed to
> +	 * the syscall fast path, so we get much better results
> +	 * fixing rsp this way.
> +	 */
> +	if (kernel && (syscall_get_nr(current, uregs->regs) >= 0)) {
> +		/* Make a copy and link it to regs pointer. */
> +		memcpy(&uregs->regs_copy, uregs->regs, sizeof(*uregs->regs));
> +		uregs->regs = &uregs->regs_copy;
> +
> +		/* And fix the rsp. */
> +		uregs->regs->sp = this_cpu_read(old_rsp);
> +	}
> +}
> +#endif

  reply	other threads:[~2012-10-03 12:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-01 17:31 [PATCH] perf x86_64: Fix rsp register for system call fast path Jiri Olsa
2012-10-02 10:44 ` Peter Zijlstra
2012-10-02 14:58   ` [PATCHv2] " Jiri Olsa
2012-10-02 15:49     ` Frederic Weisbecker
2012-10-02 16:06       ` Jiri Olsa
2012-10-02 16:16         ` Frederic Weisbecker
2012-10-03 12:29           ` [PATCHv3] " Jiri Olsa
2012-10-03 12:35             ` Frederic Weisbecker [this message]
2012-10-03 13:13               ` [PATCHv4] " Jiri Olsa
2012-10-03 13:22                 ` Peter Zijlstra
2012-10-03 13:30                   ` Jiri Olsa
2012-10-04 10:38                     ` [PATH 0/2] perf: x86_64 rsp related changes Jiri Olsa
2012-10-04 10:38                       ` [PATCH 1/2] perf x86_64: Fix rsp register for system call fast path Jiri Olsa
2012-10-04 10:38                       ` [PATCH 2/2] perf: Simplify the sample's user regs/stack retrieval Jiri Olsa

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=20121003123448.GA637@somewhere \
    --to=fweisbec@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=oleg@redhat.com \
    --cc=paulus@samba.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