Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755389AbaFQFRG (ORCPT ); Tue, 17 Jun 2014 01:17:06 -0400 Received: from mail-wi0-f172.google.com ([209.85.212.172]:50159 "EHLO mail-wi0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751895AbaFQFRE (ORCPT ); Tue, 17 Jun 2014 01:17:04 -0400 Message-ID: <539FCF48.5060705@redhat.com> Date: Tue, 17 Jun 2014 07:16:56 +0200 From: Paolo Bonzini User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Bandan Das , Nadav Amit CC: gleb@kernel.org, tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com, x86@kernel.org, kvm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/6] KVM: x86: Wrong emulation on 'xadd X, X' References: <1402837982-24959-1-git-send-email-namit@cs.technion.ac.il> <1402837982-24959-3-git-send-email-namit@cs.technion.ac.il> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Il 16/06/2014 19:38, Bandan Das ha scritto: > Nadav Amit writes: > >> The emulator does not emulate the xadd instruction correctly if the two >> operands are the same. In this (unlikely) situation the result should be the >> sum of X and X (2X) when it is currently X. The solution is to first perform >> writeback to the source, before writing to the destination. The only >> instruction which should be affected is xadd, as the other instructions that >> perform writeback to the source use the extended accumlator (e.g., RAX:RDX). >> >> Signed-off-by: Nadav Amit >> --- >> arch/x86/kvm/emulate.c | 10 +++++----- >> 1 file changed, 5 insertions(+), 5 deletions(-) >> >> diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c >> index f0b0a10..3c8d867 100644 >> --- a/arch/x86/kvm/emulate.c >> +++ b/arch/x86/kvm/emulate.c >> @@ -4711,17 +4711,17 @@ special_insn: >> goto done; >> >> writeback: >> - if (!(ctxt->d & NoWrite)) { >> - rc = writeback(ctxt, &ctxt->dst); >> - if (rc != X86EMUL_CONTINUE) >> - goto done; >> - } >> if (ctxt->d & SrcWrite) { >> BUG_ON(ctxt->src.type == OP_MEM || ctxt->src.type == OP_MEM_STR); > While we are here, I think we should replace this BUG_ON with a warning > and return X86EMUL_UNHANDLEABLE if the condition is true. Sure, please post a patch and I'll apply it right away. Paolo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/