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 1/2] uprobes: add comment with insn opcodes, mnemonics and why we dont support them
Date: Mon, 5 May 2014 21:41:00 +0200 [thread overview]
Message-ID: <20140505194100.GA26916@redhat.com> (raw)
In-Reply-To: <1399314247-7368-1-git-send-email-dvlasenk@redhat.com>
On 05/05, Denys Vlasenko wrote:
>
> + * Opcodes we'll probably never support:
> + * 6c-6f - ins,outs. SEGVs if used in userspace
> + * e4-e7 - in,out imm. SEGVs if used in userspace
> + * ec-ef - in,out acc. SEGVs if used in userspace
Well. I have no idea why they are nacked, but this is not the reason.
SEGVs are fine. Plus we have ioperm().
> + * cc - int3. SIGTRAP if used in userspace
SIGTRAP is not the reason. We do not want to enter do_int3() in UTASK_SSTEP
state with utask->active_uprobe != NULL etc. Too many potential complications.
Oleg.
next prev parent reply other threads:[~2014-05-05 19:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 18:24 [PATCH 1/2] uprobes: add comment with insn opcodes, mnemonics and why we dont support them Denys Vlasenko
2014-05-05 18:24 ` [PATCH 2/2] uprobes: fix 1-byte opcode tables Denys Vlasenko
2014-05-05 19:41 ` Oleg Nesterov [this message]
2014-05-06 17:01 ` [PATCH 1/2] uprobes: add comment with insn opcodes, mnemonics and why we dont support them Denys Vlasenko
2014-05-06 19:26 ` Oleg Nesterov
2014-05-05 22:32 ` Jim Keniston
2014-05-06 16:11 ` 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=20140505194100.GA26916@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.