Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756480AbXL3IeI (ORCPT ); Sun, 30 Dec 2007 03:34:08 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752155AbXL3Id5 (ORCPT ); Sun, 30 Dec 2007 03:33:57 -0500 Received: from mx1.redhat.com ([66.187.233.31]:56344 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752024AbXL3Id4 (ORCPT ); Sun, 30 Dec 2007 03:33:56 -0500 Message-ID: <4777574D.8010801@redhat.com> Date: Sun, 30 Dec 2007 03:31:09 -0500 From: Masami Hiramatsu User-Agent: Thunderbird 2.0.0.9 (X11/20071115) MIME-Version: 1.0 To: "H. Peter Anvin" CC: Harvey Harrison , Ananth N Mavinakayanahalli , Jim Keniston , Ingo Molnar , LKML , Thomas Gleixner Subject: Re: [PATCH] x86: Introduce REX prefix helper for kprobes References: <1198466795.6323.12.camel@brick> <47773C2D.8070600@redhat.com> <47774314.9080406@zytor.com> <47775062.4070300@redhat.com> In-Reply-To: <47775062.4070300@redhat.com> X-Enigmail-Version: 0.95.5 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 870 Lines: 31 Masami Hiramatsu wrote: > (in case of CONFIG_X86_64) > static inline int is_rex_prefix(int op) Oops, s/int op/kprobe_opcode_t opcode/ > About the name, I just used the previous inline function name. I re-think "is_REX_prefix" is better, because it is an architecture dependent notation(intel's software developers manual called it "REX prefixes"), and there is already is_IF_modifier() function in arch/x86/kernel/kprobes.c. Thanks, Best Regards, -- Masami Hiramatsu Software Engineer Hitachi Computer Products (America) Inc. Software Solutions Division e-mail: mhiramat@redhat.com, masami.hiramatsu.pt@hitachi.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/