From: Oleg Nesterov <oleg@redhat.com>
To: Denys Vlasenko <dvlasenk@redhat.com>
Cc: linux-kernel@vger.kernel.org, Jim Keniston <jkenisto@us.ibm.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH v2] uprobes: fix scratch register selection for rip-relative fixups
Date: Mon, 5 May 2014 17:45:59 +0200 [thread overview]
Message-ID: <20140505154559.GA27072@redhat.com> (raw)
In-Reply-To: <1399043040-28366-1-git-send-email-dvlasenk@redhat.com>
On 05/02, Denys Vlasenko wrote:
>
> v2: More robust checks of vex.vvvv (32-bit mode safe),
> simplified scratch reg selection code,
> moved comments around as requested by Oleg.
OK, thanks. Given that this patch was acked by Jim, I am going to
apply it. I'll try to run a couple of systemtap scripts with this
patch, but unfortunately the "full" testing is simply impossible.
Denys, I'll also include your test-case into the changelog.
And,
> static inline unsigned long *
> scratch_reg(struct arch_uprobe *auprobe, struct pt_regs *regs)
> {
> - return (auprobe->def.fixups & UPROBE_FIX_RIP_AX) ? ®s->ax : ®s->cx;
> + /* Order is important - more than one bit can be set! */
Really?
Should I remove this comment or I misread the change in riprel_analyze?
Oleg.
next prev parent reply other threads:[~2014-05-05 15:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 15:04 [PATCH v2] uprobes: fix scratch register selection for rip-relative fixups Denys Vlasenko
2014-05-02 23:43 ` Jim Keniston
2014-05-05 15:45 ` Oleg Nesterov [this message]
2014-05-05 15:47 ` Oleg Nesterov
2014-05-05 17:32 ` Denys Vlasenko
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=20140505154559.GA27072@redhat.com \
--to=oleg@redhat.com \
--cc=dvlasenk@redhat.com \
--cc=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@kernel.org \
--cc=srikar@linux.vnet.ibm.com \
/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.