[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <534DFEDC.8090503@zytor.com>
Date: Tue, 15 Apr 2014 20:54:04 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Sasha Levin <sasha.levin@...cle.com>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
CC: vegard.nossum@...cle.com, penberg@...nel.org,
jamie.iles@...cle.com, mingo@...hat.com, tglx@...utronix.de,
x86@...nel.org, linux-kernel@...r.kernel.org,
linux-mm@...r.kernel.org
Subject: Re: [PATCH 3/4] x86/insn: Extract more information about instructions
On 04/15/2014 08:47 PM, Sasha Levin wrote:
>
> Yes, if kmemcheck for some reason needs to figure out if an instruction
> is a MOV variant we'll need to list quite a few mnemonics, but that list
> will be much shorter and more readable than a corresponding list of opcodes.
>
You're completely missing my point. If you are looking at MOV, with
80%+ probability you're doing something very, very wrong, because you
will be including instructions that do something completely different
from what you thought.
This is true for a lot of the x86 instructions.
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists