Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp2844106ybn; Thu, 26 Sep 2019 19:03:49 -0700 (PDT) X-Google-Smtp-Source: APXvYqxDqwcRGcK4ESk9AWMm/RB+EdY5ovEzXXxIYXzlCRDqHKpMFHFNRsQEV/OPPFNtLI+8Xo2+ X-Received: by 2002:a17:906:4a11:: with SMTP id w17mr5728491eju.21.1569549829465; Thu, 26 Sep 2019 19:03:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1569549829; cv=none; d=google.com; s=arc-20160816; b=hJQXkeqfUaGgUJGOo6byNeAcVX5RSZKfd0wxZz2M+gf3gq8cRMVtqeM8dgSV2BkiPj SOqaSnPv2SYHvFB+fTzcGWtnIc4Ezgun9QAj+023R5eCRaqd+uiQcILE106hYSZmRbmQ +7KpR45STB7L5ylHQ0g4FcqiPofzoIF6V8FIkAx190IVRe6hKyFRqH2CWZSkW+hTjCMp G8SvD2bQ5eIK4+5/A529/eqdmwf+/3Y7zIwSCgUPU9MqQ4ImVMPlfJwAA3KIyoqXXHK3 tK7F6cGv4qEgMdmAjkYwZ3Bol9F+qX0D+mAap0lyLtc/l6q1KIdmgouQIpGBi84SdkVZ IQ0A== 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; bh=/T2U8LGaZCMC998qXvuQiGakF9ywVyCzFUplBcAKMu0=; b=y5zh9cJ+aZJ398Nw3+yxmf/m428h5vGsbDErlcvKDQtA4ASOdr+YmT4gdwCh/cEO0E 2KjGE6l+sIp0KVLE6oeo93cDN39eI1elxQsTAu67i27fQHKheY+MQyess+ENrrwufVF3 AHY9NwBwm/ru1wNn7Z9A79Bd+rAVJRcT7Ld0lQJk7lrth88gJ/1h1ZdBPzP+fKY/YvfB Tx8DH6Trpwi1xdVH9ENclQprR+rtRKlVS1QJVWSmxpufh5YpLtZqHIK66MvEiIEkh5O0 m5fnhk9RHM5PPdb8LXPYC3vDivNUWoCrBAqlOmgqLtRFVDcDydlJodj4ZH56tqwRC9D2 8fzw== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b19si2090507ejj.83.2019.09.26.19.03.24; Thu, 26 Sep 2019 19:03:49 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728027AbfI0CBf (ORCPT + 99 others); Thu, 26 Sep 2019 22:01:35 -0400 Received: from szxga05-in.huawei.com ([45.249.212.191]:2790 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726145AbfI0CBf (ORCPT ); Thu, 26 Sep 2019 22:01:35 -0400 Received: from DGGEMS408-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id F33E9AE4EF0C1B462D03; Fri, 27 Sep 2019 10:01:30 +0800 (CST) Received: from [127.0.0.1] (10.184.12.158) by DGGEMS408-HUB.china.huawei.com (10.3.19.208) with Microsoft SMTP Server id 14.3.439.0; Fri, 27 Sep 2019 10:01:20 +0800 Subject: Re: [PATCH 10/35] irqchip/gic-v4.1: VPE table (aka GICR_VPROPBASER) allocation To: Marc Zyngier , , CC: Lorenzo Pieralisi , Jason Cooper , Thomas Gleixner References: <20190923182606.32100-1-maz@kernel.org> <20190923182606.32100-11-maz@kernel.org> <155660c2-7f30-e188-ca8d-c37fabea6d97@huawei.com> <6f4ccdfd-4b63-04cb-e7c0-f069e620127f@kernel.org> <14111988-74c9-12c3-1322-1580ff6ba11f@huawei.com> From: Zenghui Yu Message-ID: <56ddfedd-5d8c-0507-c164-b04d63f51a1e@huawei.com> Date: Fri, 27 Sep 2019 09:59:16 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:64.0) Gecko/20100101 Thunderbird/64.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.184.12.158] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019/9/26 23:57, Marc Zyngier wrote: > On 26/09/2019 16:19, Zenghui Yu wrote: >> On 2019/9/25 22:41, Marc Zyngier wrote: >>> >>> Indeed. The whole idea is that ITSs and RDs can share a vPE table if >>> they are in the same affinity group (such as a socket, for example). >>> This is what is missing from v4.0 where the ITS knows about vPEs, but >>> doesn't know about residency. With that in place, the HW is able to do a >>> lot more for us. >> >> Thanks for your education! >> >> I really want to know *how* does GICv4.1 ITS know about the vPE >> residency (in hardware level)? > > Hey, I'm a SW guy, I don't design the hardware! ;-) > >> I can understand that Redistributor can easily achieve it by >> VPENDBASER's Valid and vPEID field. And it's necessary for ITS to >> know the residency so that it can determine whether it's appropriate >> to trigger default doorbell for vPE. But I have no knowledge about >> how can it be achieved in hardware details. > > My take is that the RD and the ITS can communicate over the shared > table, hence my remark above about SVPET==0. But as I said, I'm not a HW > guy. ;-) I should have asked our GIC engineers for these things. Thanks, zenghui