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>
Subject: Re: [RFC PATCH] uprobes: add comment with insn opcodes, mnemonics and why we dont support them
Date: Sun, 27 Apr 2014 13:29:25 +0200 [thread overview]
Message-ID: <20140427112925.GA17727@redhat.com> (raw)
In-Reply-To: <1398533370-8865-1-git-send-email-dvlasenk@redhat.com>
On 04/26, Denys Vlasenko wrote:
>
> After adding these, it's clear we have some awkward choices there.
> some valid instructions are prohibited from uprobing while
> several invalid ones are allowed.
Denys, both patches conflict with the pending changes in uprobe.c.
Could you resend after the next PULL request?
Oleg.
prev parent reply other threads:[~2014-04-27 11:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-26 17:29 [RFC PATCH] uprobes: add comment with insn opcodes, mnemonics and why we dont support them Denys Vlasenko
2014-04-26 17:29 ` [RFC PATCH] uprobes: simplify rip-relative handling Denys Vlasenko
2014-04-27 11:30 ` Oleg Nesterov
2014-04-27 13:13 ` Oleg Nesterov
2014-04-27 11:29 ` Oleg Nesterov [this message]
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=20140427112925.GA17727@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 \
/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.