Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp3123057ybl; Fri, 20 Dec 2019 04:19:49 -0800 (PST) X-Google-Smtp-Source: APXvYqyPblaKCGmmOcZjlThTabFLJfZXEyrsQ7J73Cj9zjLyFQ9IDWTJStDtBi6S8NGswc9/hs3Z X-Received: by 2002:a9d:20e4:: with SMTP id x91mr14313923ota.335.1576844388640; Fri, 20 Dec 2019 04:19:48 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1576844388; cv=none; d=google.com; s=arc-20160816; b=KeWXQpQMipZo2wdJZuOi//QLj7XQcnVIjsFhcUTmB2Rl9wogjtPlzogZFkoAZVB2km 1mdKli6zpCj6c0+lJm42wg1QIjFYrUIwNoTPdpu57TjWkGD+Lgsxo1rh0ikLiOqFsDqO Evshfxrihsox/LH+85E82sehoApfPC4R7cKSYZV5mq7mPxxqhaUABFjF9yC61rANZxJe EKMdP/orcZVgKytyejAKGcHNnGWW+GnQ5fb8cgWprrehwoDujwTUzV1pK8rCTF9dITBb 9RSS3PZnVyzhOsAzH5+ngwnsrPpAZy9TXXerS2rKNqgSSVqpAcOaYLztHj31vVC1t8d1 7kcQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=+uqLwzuT4/p/TrN/iMvSErZDSEuFtnJzWf7maJMj2iM=; b=y/IPmMI325MyNeqtkI1Nud33jxlWQQUPcPjZE8yhTQmcxWhQym0vB460qU2eS8/fJs WSvFz2oq6K+GWMyvWzYjHw7hgCQ+l4vhFLk/ykHkfzXXbJfZMiiqlBExQvJQE9201YaM Lj/L/6pOZ6fxJDiK0Y1fu2jq25ohCE145ffXZxikvekTDloj3pvks/O4NM03L+6tNwNP shQDaJ87m+sgfcfw3cM5ZzXUVTJmNMXNNRFjJd1drMCoWJ61NO1/wKZlyyKGZczqL4Iz hXre8PjSB9TWLiME+DMGfJVs0cjokbrRMA3Wct3DzkbvHh/FXOW8ZZXmawr4SjgDF9tE hItQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=C69pT8lW; 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=pass (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 101si470179otm.168.2019.12.20.04.19.36; Fri, 20 Dec 2019 04:19:48 -0800 (PST) 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; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=C69pT8lW; 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=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727347AbfLTMSx (ORCPT + 99 others); Fri, 20 Dec 2019 07:18:53 -0500 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:41092 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727197AbfLTMSx (ORCPT ); Fri, 20 Dec 2019 07:18:53 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1576844332; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=+uqLwzuT4/p/TrN/iMvSErZDSEuFtnJzWf7maJMj2iM=; b=C69pT8lWa53wGuSRZCB/GP4Q4UVFnSvk/8pZhiXGdv1gTMKFWhNoEhkj5BYD4zCiwPFU/T eoyrqCqVtmrY0vSEn8erqQMFnSdvqriKJVmk5FjvVNVlPL7aG0gbPdxLkmhFwH7eHu5n3q tKBMRM7K5x82MJ+Q0zD4eDKttd15nH0= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-369-pvLJVYDBOgu0tNOhkYFqLQ-1; Fri, 20 Dec 2019 07:18:48 -0500 X-MC-Unique: pvLJVYDBOgu0tNOhkYFqLQ-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 358EC185432C; Fri, 20 Dec 2019 12:18:47 +0000 (UTC) Received: from [10.36.116.117] (ovpn-116-117.ams2.redhat.com [10.36.116.117]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 2086A5C3F8; Fri, 20 Dec 2019 12:18:41 +0000 (UTC) Subject: Re: [PATCH] KVM: arm/arm64: vgic: Handle GICR_PENDBASER.PTZ filed as RAZ To: Zenghui Yu , maz@kernel.org Cc: andre.przywara@arm.com, linux-kernel@vger.kernel.org, wanghaibin.wang@huawei.com, kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org References: <20191220111833.1422-1-yuzenghui@huawei.com> From: Auger Eric Message-ID: <8f8b063c-45cf-166d-bd94-ff96831314c0@redhat.com> Date: Fri, 20 Dec 2019 13:18:40 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: <20191220111833.1422-1-yuzenghui@huawei.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Zenghui, On 12/20/19 12:18 PM, Zenghui Yu wrote: > Although guest will hardly read and use the PTZ (Pending Table Zero) > bit in GICR_PENDBASER, let us emulate the architecture strictly. > As per IHI 0069E 9.11.30, PTZ field is WO, and reads as 0. > > Signed-off-by: Zenghui Yu > --- > > Noticed when checking all fields of GICR_PENDBASER register. > But _not_ sure whether it's worth a fix, as Linux never sets > the PTZ bit before enabling LPI (set GICR_CTLR_ENABLE_LPIS). > > And I wonder under which scenarios can this bit be written as 1. > It seems difficult for software to determine whether the pending > table contains all zeros when writing this bit. > > virt/kvm/arm/vgic/vgic-mmio-v3.c | 5 ++++- > 1 file changed, 4 insertions(+), 1 deletion(-) > > diff --git a/virt/kvm/arm/vgic/vgic-mmio-v3.c b/virt/kvm/arm/vgic/vgic-mmio-v3.c > index 7dfd15dbb308..ebc218840fc2 100644 > --- a/virt/kvm/arm/vgic/vgic-mmio-v3.c > +++ b/virt/kvm/arm/vgic/vgic-mmio-v3.c > @@ -414,8 +414,11 @@ static unsigned long vgic_mmio_read_pendbase(struct kvm_vcpu *vcpu, > gpa_t addr, unsigned int len) > { > struct vgic_cpu *vgic_cpu = &vcpu->arch.vgic_cpu; > + u64 value = vgic_cpu->pendbaser; > > - return extract_bytes(vgic_cpu->pendbaser, addr & 7, len); > + value &= ~GICR_PENDBASER_PTZ; > + > + return extract_bytes(value, addr & 7, len); > } > > static void vgic_mmio_write_pendbase(struct kvm_vcpu *vcpu, > Reviewed-by: Eric Auger Thanks Eric