From: Jeff Epler <jepler@unpythonic.net>
To: Eugene Shatokhin <eugene.shatokhin@rosalab.ru>
Cc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Ingo Molnar <mingo@kernel.org>,
Andy Lutomirski <luto@amacapital.net>,
Ingo Molnar <mingo@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] kprobes/x86: Use 16 bytes for each instruction slot again
Date: Thu, 4 Jun 2015 09:42:18 -0500 [thread overview]
Message-ID: <20150604144218.GA50871@unpythonic.net> (raw)
In-Reply-To: <1433318051-12509-1-git-send-email-eugene.shatokhin@rosalab.ru>
On Wed, Jun 03, 2015 at 10:54:11AM +0300, Eugene Shatokhin wrote:
> --- a/kernel/kprobes.c
> +++ b/kernel/kprobes.c
> @@ -57,7 +57,6 @@
> #define KPROBE_HASH_BITS 6
> #define KPROBE_TABLE_SIZE (1 << KPROBE_HASH_BITS)
>
> -
> /*
> * Some oddball architectures like 64bit powerpc have function descriptors
> * so this must be overridable.
Unintentional whitespace change
prev parent reply other threads:[~2015-06-04 14:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 16:32 [PATCH 0/2] kprobes/x86: Allow "boost" for 10- and 11-byte instructions Eugene Shatokhin
2015-06-01 16:32 ` [PATCH 1/2] kprobes/x86: boost: Fix checking if there is enough room for a jump Eugene Shatokhin
2015-06-01 21:51 ` Masami Hiramatsu
2015-06-01 16:32 ` [PATCH 2/2] kprobes/x86: Use 16 bytes for each instruction slot again Eugene Shatokhin
2015-06-01 17:04 ` Andy Lutomirski
2015-06-01 21:49 ` Masami Hiramatsu
2015-06-01 21:57 ` Andy Lutomirski
2015-06-02 21:42 ` Masami Hiramatsu
2015-06-02 5:44 ` Ingo Molnar
2015-06-02 21:46 ` Masami Hiramatsu
2015-06-02 21:55 ` Andy Lutomirski
2015-06-04 21:59 ` Masami Hiramatsu
2015-06-03 7:28 ` Ingo Molnar
2015-06-01 21:58 ` Masami Hiramatsu
2015-06-02 5:47 ` Ingo Molnar
2015-06-01 21:44 ` [PATCH 0/2] kprobes/x86: Allow "boost" for 10- and 11-byte instructions Masami Hiramatsu
2015-06-03 7:54 ` [PATCH v2 2/2] kprobes/x86: Use 16 bytes for each instruction slot again Eugene Shatokhin
2015-06-04 14:42 ` Jeff Epler [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=20150604144218.GA50871@unpythonic.net \
--to=jepler@unpythonic.net \
--cc=eugene.shatokhin@rosalab.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox