On 04/15/2014 11:54 PM, H. Peter Anvin wrote: > 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.
Right, but assuming that the AND example I presented earlier makes sense, I can't create mnemonic entries only for instructions where doing so would "probably" be right. If there are use cases where working with mnemonics is correct, we should be doing that in kmemcheck. If the way kmemcheck deals with mnemonics is incorrect we should go ahead and fix kmemcheck. Thanks, Sasha -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/