Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp691984ybv; Wed, 19 Feb 2020 07:19:59 -0800 (PST) X-Google-Smtp-Source: APXvYqw9BSb8OO2SZHqYdBQpgfgCXtwX362bLug0Q1npBnirjdOzAWp38yyRmOJL0Xjrv0kU6lnu X-Received: by 2002:a9d:4541:: with SMTP id p1mr20520898oti.199.1582125599706; Wed, 19 Feb 2020 07:19:59 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1582125599; cv=none; d=google.com; s=arc-20160816; b=L91qsX3OTiQ+Ru86fFmzmse0hSF1dXF8XhwNF9jKxgmf7WDakOZt9NVjtF3Xohm8SX YxsSx+y+mo4iNn0lVhNrOUivT+K0jDEYt3JNLkKUs4GAyWr2nVPpXo/RY2ic1pcU0sN7 S9XeCBMg2RjGkffklf4FmgBs5W6V20aJkADpIa6aZueaQj5kzM1DdY/2+vIi+HIZnGbf 2i20nuPY2T1WYM/hhM5uk7L6JNnZgv1ER0htL1psu/GzGBRoE0ExzR8/cKj/Gt2bQka/ AUCH1Cz7JcxDFhD0Eqp4VU/kV3GB0K9VG454A7FUJ0oMbkM7cqsQUCmew2PFpwBfif4o QRww== 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:references:cc:to:from:subject; bh=GCiw7BbA5DFR+XnhoHS7gp4ZmtYKdAFreNn22kTNa0U=; b=DFs6LSUUJAOljI39uE0VdlT+kzvuje9ZKrnmNeYEREuB1+AygMGEQ3UXVnThdlJcRZ /WVGDqxSdLbVO0PGF5D6XxvUTlWAmuPc2cAyKaGSoLGQz4dpQaSsmg3Oje7DOdfl83/g 2KKx92V/X6FKzMWsoVyjnHwAUF1FJ1/TIfTv9enIKYV88V95xEjpadwFrIdpjrWxTWNI th+bSEbwgr3dZiyrNa4Nfvoot8c8WCQJ6ML6UFIGuVvwhlBgvNWSvoCi0tyB5pA9GabM 2tqUawz90kinfYTaLm0aENXqc8+LHSrW5PuWCUak7aPeykLv11lEyklvq494EO+QzcIt iE7w== 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 k19si17926otp.33.2020.02.19.07.19.46; Wed, 19 Feb 2020 07:19:59 -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; 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 S1727485AbgBSPSg (ORCPT + 99 others); Wed, 19 Feb 2020 10:18:36 -0500 Received: from szxga05-in.huawei.com ([45.249.212.191]:10221 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727429AbgBSPSf (ORCPT ); Wed, 19 Feb 2020 10:18:35 -0500 Received: from DGGEMS413-HUB.china.huawei.com (unknown [172.30.72.60]) by Forcepoint Email with ESMTP id 8FBB9C63BB00B34477CF; Wed, 19 Feb 2020 23:18:27 +0800 (CST) Received: from [127.0.0.1] (10.173.222.27) by DGGEMS413-HUB.china.huawei.com (10.3.19.213) with Microsoft SMTP Server id 14.3.439.0; Wed, 19 Feb 2020 23:18:19 +0800 Subject: Re: [PATCH v4 08/20] irqchip/gic-v4.1: Plumb get/set_irqchip_state SGI callbacks From: Zenghui Yu To: Marc Zyngier CC: , , , , Lorenzo Pieralisi , Jason Cooper , "Robert Richter" , Thomas Gleixner , "Eric Auger" , James Morse , "Julien Thierry" , Suzuki K Poulose References: <20200214145736.18550-1-maz@kernel.org> <20200214145736.18550-9-maz@kernel.org> <4b7f71f1-5e7f-e6af-f47d-7ed0d3a8739f@huawei.com> <75597af0d2373ac4d92d8162a1338cbb@kernel.org> <19a7c193f0e4b97343e822a35f0911ed@kernel.org> <8db95a86-0981-710b-6c82-be7f7f844151@huawei.com> Message-ID: <8c538d2e-5ec8-0fd0-8999-e43a847df4c1@huawei.com> Date: Wed, 19 Feb 2020 23:18:16 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.2.0 MIME-Version: 1.0 In-Reply-To: <8db95a86-0981-710b-6c82-be7f7f844151@huawei.com> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Originating-IP: [10.173.222.27] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2020/2/19 19:50, Zenghui Yu wrote: > 3. it looks like KVM makes the assumption that the per-RD MMIO region > will only be accessed by the associated VCPU?  But I think this's not > restricted by the architecture, we can do it better.  Or I've just > missed some important points here. (After some basic tests, KVM actually does the right thing!) So I must have some mis-understanding on this point, please ignore it. I'll dig it further myself, sorry for the noisy. Thanks, Zenghui