linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Ulrich Drepper <drepper@gmail.com>
Cc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	x86@kernel.org, pp-manager@sdl.hitachi.co.jp
Subject: Re: ANDN and Group 17 in x86-opcode-map.txt
Date: Tue, 17 Jan 2012 11:21:51 -0800	[thread overview]
Message-ID: <4F15CA4F.9060005@zytor.com> (raw)
In-Reply-To: <CAOPLpQdq5SuVo9=023CYhbFLAX9rONyjmYq7jJkqc5xwctW5eA@mail.gmail.com>

On 01/17/2012 11:14 AM, Ulrich Drepper wrote:
> The Intel documentation at
> 
> http://software.intel.com/file/36945
> 
> shows the ANDN opcode and Group 17 with encoding f2 and f3 encoding
> respectively.  The current version of x86-opcode-map.txt shows them
> with f3 and f4.  Unless someone can point to documentation which shows
> the currently used encoding the following patch be applied.
> 
> Signed-off-by: Ulrich Drepper <drepper@gmail.com>
> 

Looks right to me.  Masami, I assume this was just a transcription error?

Acked-by: H. Peter Anvin <hpa@zytor.com>


-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  reply	other threads:[~2012-01-17 19:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-17 19:14 ANDN and Group 17 in x86-opcode-map.txt Ulrich Drepper
2012-01-17 19:21 ` H. Peter Anvin [this message]
2012-01-18  3:08   ` Masami Hiramatsu
2012-01-17 22:43 ` [tip:x86/urgent] x86, opcode: ANDN and Group 17 in x86-opcode-map. txt tip-bot for Ulrich Drepper

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=4F15CA4F.9060005@zytor.com \
    --to=hpa@zytor.com \
    --cc=drepper@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@redhat.com \
    --cc=pp-manager@sdl.hitachi.co.jp \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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).