From: Masami Hiramatsu <mhiramat@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Przemysssaw Paweeeczyk <przemyslaw@pawelczyk.it>,
Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
lkml <linux-kernel@vger.kernel.org>,
systemtap <systemtap@sources.redhat.com>,
kvm <kvm@vger.kernel.org>, Jim Keniston <jkenisto@us.ibm.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Andi Kleen <ak@linux.intel.com>,
Vegard Nossum <vegard.nossum@gmail.com>,
Avi Kivity <avi@redhat.com>
Subject: Re: [PATCH -tip v5 1/7] x86: instruction decorder API
Date: Wed, 13 May 2009 10:35:55 -0400 [thread overview]
Message-ID: <4A0ADACB.8030205@redhat.com> (raw)
In-Reply-To: <20090513094326.GA22281@redhat.com>
Gleb Natapov wrote:
> On Wed, May 13, 2009 at 11:35:16AM +0200, Przemysssaw Paweeeczyk wrote:
>> On Wed, May 13, 2009 at 10:23, Gleb Natapov <gleb@redhat.com> wrote:
>>> On Fri, May 08, 2009 at 08:48:42PM -0400, Masami Hiramatsu wrote:
>>>> +++ b/arch/x86/scripts/gen-insn-attr-x86.awk
>>>> @@ -0,0 +1,314 @@
>>>> +#!/bin/awk -f
>>> On some distributions (debian) it is /usr/bin/awk.
>> True, but on most of them (all?) there is also an appropriate link in /bin.
> Nope, not on debian testing. Although I assume if kernel compilation
> will start to fail it will appear :)
>
>> If shebang could have more that one argument, then '/usr/bin/env awk
>> -f' would be the best solution I think.
Ah, I see.
Actually, it will be executed from Makefile with 'awk -f'.
> --- a/arch/x86/lib/Makefile
> +++ b/arch/x86/lib/Makefile
> @@ -2,12 +2,21 @@
> # Makefile for x86 specific library files.
> #
>
> +quiet_cmd_inat_tables = GEN $@
> + cmd_inat_tables = awk -f $(srctree)/arch/x86/scripts/gen-insn-attr-x86.awk $(srctree)/arch/x86/lib/x86-opcode-map.txt > $@
> +
So, if awk is on the PATH, it will pass.
Maybe, I need to add 'HOSTAWK = awk' line in Makefile.
Thank you,
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America) Inc.
Software Solutions Division
e-mail: mhiramat@redhat.com
next prev parent reply other threads:[~2009-05-13 14:34 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-09 0:48 [PATCH -tip v5 0/7] tracing: kprobe-based event tracer and x86 instruction decoder Masami Hiramatsu
2009-05-09 0:48 ` [PATCH -tip v5 1/7] x86: instruction decorder API Masami Hiramatsu
2009-05-11 9:27 ` Christoph Hellwig
2009-05-11 14:36 ` Masami Hiramatsu
2009-05-13 8:23 ` Gleb Natapov
2009-05-13 9:35 ` Przemysław Pawełczyk
2009-05-13 9:43 ` Gleb Natapov
2009-05-13 14:35 ` Masami Hiramatsu [this message]
2009-05-13 15:20 ` Gleb Natapov
2009-05-09 0:48 ` [PATCH -tip v5 2/7] kprobes: checks probe address is instruction boudary on x86 Masami Hiramatsu
2009-05-11 14:20 ` Steven Rostedt
2009-05-11 15:01 ` Masami Hiramatsu
2009-05-11 15:14 ` Masami Hiramatsu
2009-05-11 15:22 ` Steven Rostedt
2009-05-11 18:21 ` Masami Hiramatsu
2009-05-09 0:48 ` [PATCH -tip v5 3/7] kprobes: cleanup fix_riprel() using insn decoder " Masami Hiramatsu
2009-05-09 0:48 ` [PATCH -tip v5 4/7] tracing: add kprobe-based event tracer Masami Hiramatsu
2009-05-09 16:36 ` Frédéric Weisbecker
2009-05-09 17:33 ` Masami Hiramatsu
2009-05-11 21:26 ` Frederic Weisbecker
2009-05-11 9:32 ` Christoph Hellwig
2009-05-11 10:53 ` Ingo Molnar
2009-05-11 15:28 ` Frank Ch. Eigler
2009-05-09 0:49 ` [PATCH -tip v5 5/7] x86: fix kernel_trap_sp() Masami Hiramatsu
2009-05-11 9:28 ` Christoph Hellwig
2009-05-11 13:48 ` Masami Hiramatsu
2009-05-09 0:49 ` [PATCH -tip v5 6/7] x86: add pt_regs register and stack access APIs Masami Hiramatsu
2009-05-09 0:49 ` [PATCH -tip v5 7/7] tracing: add arguments support on kprobe-based event tracer Masami Hiramatsu
2009-05-11 14:35 ` Steven Rostedt
2009-05-09 4:43 ` [PATCH -tip v5 0/7] tracing: kprobe-based event tracer and x86 instruction decoder Ingo Molnar
2009-05-11 14:40 ` Masami Hiramatsu
2009-05-11 14:56 ` Steven Rostedt
2009-05-11 20:05 ` Masami Hiramatsu
2009-05-11 21:47 ` Ingo Molnar
2009-05-12 22:03 ` Masami Hiramatsu
2009-05-13 13:21 ` Ingo Molnar
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=4A0ADACB.8030205@redhat.com \
--to=mhiramat@redhat.com \
--cc=ak@linux.intel.com \
--cc=ananth@in.ibm.com \
--cc=avi@redhat.com \
--cc=fweisbec@gmail.com \
--cc=gleb@redhat.com \
--cc=hpa@zytor.com \
--cc=jkenisto@us.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=przemyslaw@pawelczyk.it \
--cc=rostedt@goodmis.org \
--cc=systemtap@sources.redhat.com \
--cc=vegard.nossum@gmail.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