From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 61822C4167B for ; Wed, 6 Dec 2023 08:18:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:In-Reply-To:References: Message-ID:Date:Subject:CC:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=ENET2VNskzdbPJvlc4IBsNAnAqHh9MQLmk8xtfx1+y8=; b=AGDFMzBbcPvaNh 82MDvLshLTXYylKMGJkHepU8FioKb0viP7T57FzumrvBb8Rrdc+YuKu6HKoHrvJhx510R7vaSHenU 71Ef2MjbFtd8Xj7OZBzz9pgtltJGjR0JW4Rv4cX30Ovr1MF2S37vWCVW+3OFkbfUpqWcYI6nmz8Xu YDnMN6lMH8ZZvXh5W8YN1S3XnhpzEv01I4I/dfq2cA1zSEfw8fr7f3Bhxw8qihk/G7UXbS7ZQaais jUPerlYx6jf7iIDyhqU7UrZd5fSUjwJJS0b1fItU+ex4cpKxf6YfRzKCpVEKfWAsedV8sUt8UQKbX RAAA/PlSKqcVwjUhRZiw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1rAn6l-009PIF-30; Wed, 06 Dec 2023 08:18:15 +0000 Received: from szxga08-in.huawei.com ([45.249.212.255]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1rAn6i-009PG3-01 for linux-arm-kernel@lists.infradead.org; Wed, 06 Dec 2023 08:18:14 +0000 Received: from kwepemm000007.china.huawei.com (unknown [172.30.72.56]) by szxga08-in.huawei.com (SkyGuard) with ESMTP id 4SlVYM2HN3z1Q6DC; Wed, 6 Dec 2023 16:14:15 +0800 (CST) Received: from lhrpeml500005.china.huawei.com (7.191.163.240) by kwepemm000007.china.huawei.com (7.193.23.189) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.35; Wed, 6 Dec 2023 16:18:01 +0800 Received: from lhrpeml500005.china.huawei.com ([7.191.163.240]) by lhrpeml500005.china.huawei.com ([7.191.163.240]) with mapi id 15.01.2507.035; Wed, 6 Dec 2023 08:17:59 +0000 From: Shameerali Kolothum Thodi To: Catalin Marinas , Marc Zyngier CC: "ankita@nvidia.com" , "jgg@nvidia.com" , "oliver.upton@linux.dev" , "suzuki.poulose@arm.com" , yuzenghui , "will@kernel.org" , "ardb@kernel.org" , "akpm@linux-foundation.org" , "gshan@redhat.com" , "aniketa@nvidia.com" , "cjia@nvidia.com" , "kwankhede@nvidia.com" , "targupta@nvidia.com" , "vsethi@nvidia.com" , "acurrid@nvidia.com" , "apopple@nvidia.com" , "jhubbard@nvidia.com" , "danw@nvidia.com" , "mochs@nvidia.com" , "kvmarm@lists.linux.dev" , "kvm@vger.kernel.org" , "lpieralisi@kernel.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linyufeng (A)" Subject: RE: [PATCH v2 1/1] KVM: arm64: allow the VM to select DEVICE_* and NORMAL_NC for IO memory Thread-Topic: [PATCH v2 1/1] KVM: arm64: allow the VM to select DEVICE_* and NORMAL_NC for IO memory Thread-Index: AQHaJyt5vUQXGRK0CEWl1So2KZfV67CaaoMAgAAm7ICAACpz4IABLXlA Date: Wed, 6 Dec 2023 08:17:59 +0000 Message-ID: References: <20231205033015.10044-1-ankita@nvidia.com> <86fs0hatt3.wl-maz@kernel.org> <296657c5b09f46a1ac6e4d993fbc0875@huawei.com> In-Reply-To: <296657c5b09f46a1ac6e4d993fbc0875@huawei.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.202.227.28] MIME-Version: 1.0 X-CFilter-Loop: Reflected X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20231206_001812_394966_ACE0472B X-CRM114-Status: GOOD ( 22.60 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org > -----Original Message----- > From: Shameerali Kolothum Thodi > Sent: Tuesday, December 5, 2023 2:17 PM > To: 'Catalin Marinas' ; Marc Zyngier > > Cc: ankita@nvidia.com; jgg@nvidia.com; oliver.upton@linux.dev; > suzuki.poulose@arm.com; yuzenghui ; > will@kernel.org; ardb@kernel.org; akpm@linux-foundation.org; > gshan@redhat.com; aniketa@nvidia.com; cjia@nvidia.com; > kwankhede@nvidia.com; targupta@nvidia.com; vsethi@nvidia.com; > acurrid@nvidia.com; apopple@nvidia.com; jhubbard@nvidia.com; > danw@nvidia.com; mochs@nvidia.com; kvmarm@lists.linux.dev; > kvm@vger.kernel.org; lpieralisi@kernel.org; linux-kernel@vger.kernel.org; > linux-arm-kernel@lists.infradead.org; linyufeng (A) > > Subject: RE: [PATCH v2 1/1] KVM: arm64: allow the VM to select DEVICE_* > and NORMAL_NC for IO memory > > > > > -----Original Message----- > > From: Catalin Marinas > > Sent: Tuesday, December 5, 2023 11:41 AM > > To: Marc Zyngier > > Cc: ankita@nvidia.com; Shameerali Kolothum Thodi > > ; jgg@nvidia.com; > > oliver.upton@linux.dev; suzuki.poulose@arm.com; yuzenghui > > ; will@kernel.org; ardb@kernel.org; > akpm@linux- > > foundation.org; gshan@redhat.com; aniketa@nvidia.com; > cjia@nvidia.com; > > kwankhede@nvidia.com; targupta@nvidia.com; vsethi@nvidia.com; > > acurrid@nvidia.com; apopple@nvidia.com; jhubbard@nvidia.com; > > danw@nvidia.com; mochs@nvidia.com; kvmarm@lists.linux.dev; > > kvm@vger.kernel.org; lpieralisi@kernel.org; linux-kernel@vger.kernel.org; > > linux-arm-kernel@lists.infradead.org > > Subject: Re: [PATCH v2 1/1] KVM: arm64: allow the VM to select DEVICE_* > > and NORMAL_NC for IO memory > > > > + Lorenzo, he really needs to be on this thread. > > > > On Tue, Dec 05, 2023 at 09:21:28AM +0000, Marc Zyngier wrote: > > > On Tue, 05 Dec 2023 03:30:15 +0000, > > > wrote: > > > > From: Ankit Agrawal > > > > > > > > Currently, KVM for ARM64 maps at stage 2 memory that is considered > > device > > > > (i.e. it is not RAM) with DEVICE_nGnRE memory attributes; this setting > > > > overrides (as per the ARM architecture [1]) any device MMIO mapping > > > > present at stage 1, resulting in a set-up whereby a guest operating > > > > system cannot determine device MMIO mapping memory attributes on > > its > > > > own but it is always overridden by the KVM stage 2 default. > > [...] > > > Despite the considerable increase in the commit message length, a > > > number of questions are left unanswered: > > > > > > - Shameer reported a regression on non-FWB systems, breaking device > > > assignment: > > > > > > > > > https://lore.kernel.org/all/af13ed63dc9a4f26a6c958ebfa77d78a@huawei.co > > m/ > > > > This referred to the first patch in the old series which was trying to > > make the Stage 2 cacheable based on the vma attributes. That patch has > > been dropped for now. It would be good if Shameer confirms this was the > > problem. > > > > Yes, that was related to the first patch. We will soon test this on both FWB > and > non-FWB platforms and report back. > Thanks to Yufeng, the test on both FWB and non-FWB platforms with a GPU dev assignment looks fine with this patch. Shameer _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel