From: "H. Peter Anvin" <hpa@zytor.com>
To: Jim Keniston <jkenisto@us.ibm.com>
Cc: Masami Hiramatsu <mhiramat@redhat.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: Thu, 16 Apr 2009 17:08:30 -0700 [thread overview]
Message-ID: <49E7C87E.8000202@zytor.com> (raw)
In-Reply-To: <1239926776.5883.17.camel@dyn9047018094.beaverton.ibm.com>
Jim Keniston wrote:
>
> It looks like AT2(Ev,Gv) would yield the same bits as AT2(Gv,Ev). It'd
> be nice not to lose the operand-order information. And we'd have to
> make clear whether which notation we're using -- src,dest as in the gnu
> assembler, or dest,src as in the AMD (and Intel?) manuals.
>
Since the information would come from the manuals, I would recommend
following them (dst first.)
-hpa
next prev parent reply other threads:[~2009-04-17 0:08 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
2009-04-17 0:06 ` Jim Keniston
2009-04-17 0:08 ` H. Peter Anvin [this message]
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=49E7C87E.8000202@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).