From: "H. Peter Anvin" <hpa@zytor.com>
To: Masami Hiramatsu <mhiramat@redhat.com>
Cc: Jim Keniston <jkenisto@us.ibm.com>, Ingo Molnar <mingo@elte.hu>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Andi Kleen <andi@firstfloor.org>,
kvm@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
systemtap-ml <systemtap@sources.redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Vegard Nossum <vegard.nossum@gmail.com>,
Avi Kivity <avi@redhat.com>, Roland McGrath <roland@redhat.com>
Subject: Re: [PATCH -tip 3/6 V4.1] x86: instruction decorder API
Date: Fri, 17 Apr 2009 11:07:44 -0700 [thread overview]
Message-ID: <49E8C570.7030708@zytor.com> (raw)
In-Reply-To: <49E884C2.9030409@redhat.com>
Masami Hiramatsu wrote:
>
> Aah, I see. So we'd better make a parser which generates internal
> data structure from genuine opcode map in compilation time.
>
> And I changed my mind about internal data structure too.
> In this version, I'll use a smallest bits which are needed
> for the decoder.
>
Yes, and with a proper compile-time parser, that kind of things can be
done, and be changed later if it is no longer appropriate.
-hpa
next prev parent reply other threads:[~2009-04-17 18:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 17:24 [PATCH -tip 3/6 V4] x86: instruction decorder API Masami Hiramatsu
2009-04-03 23:29 ` [PATCH -tip 3/6 V4.1] " Masami Hiramatsu
2009-04-03 23:43 ` H. Peter Anvin
2009-04-04 0:37 ` Masami Hiramatsu
2009-04-06 22:48 ` Jim Keniston
2009-04-06 22:55 ` H. Peter Anvin
2009-04-16 23:31 ` Masami Hiramatsu
2009-04-16 23:39 ` H. Peter Anvin
2009-04-17 13:31 ` Masami Hiramatsu
2009-04-17 18:07 ` H. Peter Anvin [this message]
2009-04-17 0:06 ` Jim Keniston
2009-04-17 0:08 ` H. Peter Anvin
2009-04-22 0:17 ` Masami Hiramatsu
2009-04-23 0:47 ` Jim Keniston
2009-04-23 17:29 ` Masami Hiramatsu
2009-04-23 22:22 ` Jim Keniston
2009-04-24 3:53 ` Masami Hiramatsu
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=49E8C570.7030708@zytor.com \
--to=hpa@zytor.com \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ananth@in.ibm.com \
--cc=andi@firstfloor.org \
--cc=avi@redhat.com \
--cc=fweisbec@gmail.com \
--cc=jkenisto@us.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.com \
--cc=mingo@elte.hu \
--cc=roland@redhat.com \
--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 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.