Received: by 2002:ac0:bc90:0:0:0:0:0 with SMTP id a16csp658422img; Fri, 22 Mar 2019 06:05:11 -0700 (PDT) X-Google-Smtp-Source: APXvYqy7Ih58bwB3NZIgf4sfCY+pwnXTQYbGyMNmTk2HDXDYOHxa012qIs1SjCCHrSA90bZFqME5 X-Received: by 2002:a63:1003:: with SMTP id f3mr273223pgl.227.1553259910939; Fri, 22 Mar 2019 06:05:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553259910; cv=none; d=google.com; s=arc-20160816; b=SlGeTVuRTCRKVdzCOlPtFWB0xzPLMV40Db+rjOZLMzuh+zaZwFtxpiVuW74Y9okTew HwhpZfhje/obMdsfZ4+1pOrixn96fEUN9mjhJ70jXDtvE7wHVK6OVIh+lBgnzabOFL8p iNxZHK5rm5n6DiP9eIr+z8TdB74LKY6yzXfTqLiA8RsvohbwQcEJB+zDqMR+BmWZiTdt /wgwKL1b529Dd7WLqRPcMsJ5DvCWPfYaTtc8dIZPlZXq6f4HOm77UBpkTDMinM8tk1s1 j+yhOarhFB92o2+TUgbzaW6D0KXF5IGSR6OSfdO57Y8oHkf/yP5wqMoEvkgJxQiMar7N tvoA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from; bh=dzohx9uLBVWg4NAwXMeyvzY5YQucALzki7Y15eX3710=; b=MFxGUd0qHvSRv+L4g34of74ES2ujn9gCqFbTSHju82qK9pEva6JkeM0vDZ6NJxfDVV c+zW7a+B+k4N0bL6CkRwvARbX074pTsOyZlljYHlnRVJFLrJwYOf7nLGi8OtcgkQwJFV mUqa0jK9kxuofgXWbj83HLCeIu027d+dgi1ffJpmvXlyxTRuXuVEHNLMp1hP7G191NQ7 IUKpCW8+5rdJ9pNQ85saddwnZsHAbD7MCSaiP5rJPmFmjYbMS1AxLPtVS+VM9FPla0aM eyJjreQtqgn5zafJ3lvJs+MwRX0waXwoHRF+N/Cd3ym9tLZvb4SQt9tN3mjPDLF9gKym UjhQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m3si6388078pgq.343.2019.03.22.06.04.53; Fri, 22 Mar 2019 06:05:10 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731452AbfCVNEG (ORCPT + 99 others); Fri, 22 Mar 2019 09:04:06 -0400 Received: from mail-wr1-f66.google.com ([209.85.221.66]:42169 "EHLO mail-wr1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730977AbfCVNEF (ORCPT ); Fri, 22 Mar 2019 09:04:05 -0400 Received: by mail-wr1-f66.google.com with SMTP id g3so2260064wrx.9 for ; Fri, 22 Mar 2019 06:04:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=dzohx9uLBVWg4NAwXMeyvzY5YQucALzki7Y15eX3710=; b=cgWVPfZcJOwGx9Q06MaqYlsD+zrSq+6OfZKnQpX0reP85NDklRmFeWxEOrACars9d0 J6+WlcLMnB1cr+PUCAfPphfmYRzuHInzu6NBL5eU0G6/l4vwZzbGhwY1PejuUU9Iv2HB 0PVDWdslmBxDSOUFiryqM+RECeuiBIzjbdF+6C/g86joKYSqt+8fehMO12XaopplrdBH OlQe9atu/v1AIO/im+YJajZFmmv27wIOP44dbjJrDqIjbjU+qL4UC1WjIacuM7CkYUv9 ZZYsr9OgURCD7VHxxzxaBHLtEeMqqnuqMDtV7nFgbaYBUGZa+yOkP5ovqXyRGDpjSAmq BXdg== X-Gm-Message-State: APjAAAVSOvidQ3CPXlvKZFx7Pw7OvlikAg3w2UQ3Xw/bVVASQApHFBR8 LavgFlnFIazq/899K8OXDhuadTTdmrM= X-Received: by 2002:a5d:43c9:: with SMTP id v9mr6313895wrr.269.1553259843463; Fri, 22 Mar 2019 06:04:03 -0700 (PDT) Received: from vitty.brq.redhat.com (nat-pool-brq-t.redhat.com. [213.175.37.10]) by smtp.gmail.com with ESMTPSA id 13sm8215249wmj.33.2019.03.22.06.04.01 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 22 Mar 2019 06:04:02 -0700 (PDT) From: Vitaly Kuznetsov To: "Suthikulpanit\, Suravee" Cc: "joro\@8bytes.org" , "pbonzini\@redhat.com" , "rkrcmar\@redhat.com" , "linux-kernel\@vger.kernel.org" , "kvm\@vger.kernel.org" Subject: Re: [PATCH] svm/avic: Fix invalidate logical APIC id entry In-Reply-To: <20190322101706.9377-1-suravee.suthikulpanit@amd.com> References: <20190322101706.9377-1-suravee.suthikulpanit@amd.com> Date: Fri, 22 Mar 2019 14:04:01 +0100 Message-ID: <87ef6zcb7i.fsf@vitty.brq.redhat.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org "Suthikulpanit, Suravee" writes: > Only clear the valid bit when invalidate logical APIC id entry. > The current logic clear the valid bit, but also set the rest of > the bits (including reserved bits) to 1. > > Fixes: 98d90582be2e ('svm: Fix AVIC DFR and LDR handling') > Signed-off-by: Suravee Suthikulpanit > --- > arch/x86/kvm/svm.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c > index 7a4ce1a22ca0..f4fb766e474c 100644 > --- a/arch/x86/kvm/svm.c > +++ b/arch/x86/kvm/svm.c > @@ -4640,7 +4640,7 @@ static void avic_invalidate_logical_id_entry(struct kvm_vcpu *vcpu) > u32 *entry = avic_get_logical_id_entry(vcpu, svm->ldr_reg, flat); > > if (entry) > - WRITE_ONCE(*entry, (u32) ~AVIC_LOGICAL_ID_ENTRY_VALID_MASK); > + WRITE_ONCE(*entry, (u32)(*entry & ~AVIC_LOGICAL_ID_ENTRY_VALID_MASK)); I'm not sure how important this is, but this change creates a tiny time window between reading from *entry and writing there. Should we use atomic bitops instead? > } > > static int avic_handle_ldr_update(struct kvm_vcpu *vcpu) -- Vitaly