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 3EB7EC3DA4A for ; Fri, 2 Aug 2024 17:31: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:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Content-Type:MIME-Version: Message-ID:Date:References:In-Reply-To:Subject:Cc:To:From:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=u+ebwk+BNbzquNMkgUYsWeVVLW8Lr42rftw+FPJno+I=; b=Y0lLEHTNwicX+IM3kGFB28OPhr qOKrZFR/Y8bMzwdKXCg0oHbBUqVNluplDWcYQQpRzkVysorrX7G0BoFviTlLz9G276RJayVMToOXN gDCSX9+kN+w0zc6QdRjKIj0ItiRnk+JRr7d8/wqvQj4h5X3qnneK7scGI76tVbDpX1+MUJ2eB1wxx ffBJzHJ6VY6CQMljTIgMekNXG4KOE87ZNqcbwlifyDHmKzk/YX4KJVU+eNvemsNrXvGVDiMQFPx2r rxvRdu29JBYFBC1WKDoGtQ+E6ErKRfGgfWtId3ejgGSkRihbMoUF63/VWyJXFFWQ+tUIrrxrj591x sARddugQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1sZw7l-00000009biR-0zt4; Fri, 02 Aug 2024 17:31:29 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1sZuxF-00000009RUi-3reR for linux-arm-kernel@lists.infradead.org; Fri, 02 Aug 2024 16:16:35 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id CE4E5628BC; Fri, 2 Aug 2024 16:16:32 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id C51FEC32782; Fri, 2 Aug 2024 16:16:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1722615392; bh=7tBPJDGBSXQXrJPXcK1OlbhN3CEcxQySVnphOx8+TZY=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=lyuHUg7D90JWU3TbW78IU7LH8ClvNjA0D1v1UhYw2qsd8JOgCvGUCIh8/xEs8OpCm 5KK4YT1Di2MGWl9khw42YSkN5XcqPPOE3yxQSQlXLtVqxUXhdfXnpqmIHYHaAWXfvy hgyF5u7Vro3hVkM/hPRw6FQHja/TI4SxwY9yKxBRoGFJ2Tc5HtLMlWnTfqfSdXwO1w ktVBVf5gJWu5/LgCPy1sxarVqeWXrsXl67SXPQ1f4GXdqn/ZRv5TgmWiivWG89fcHK 7NepxvyRUbfeU6mpeE/55GL2oZqHjNFITZ6DoU7yfOomeTCLHYaUKTs2xDUfZjoWHm WBq8wstjiurgw== X-Mailer: emacs 31.0.50 (via feedmail 11-beta-1 I) From: Aneesh Kumar K.V To: Catalin Marinas Cc: Will Deacon , linux-arm-kernel@lists.infradead.org, Sudeep Holla , Lorenzo Pieralisi , Suzuki Poulose , Steven Price , Oliver Upton , Marc Zyngier , linux-coco@lists.linux.dev Subject: Re: [PATCH 1/6] firmware/smccc: Call arch-specific hook on discovering KVM services In-Reply-To: References: <20240730151113.1497-1-will@kernel.org> <20240730151113.1497-2-will@kernel.org> <20240731155045.GA3296@willie-the-truck> Date: Fri, 02 Aug 2024 21:46:24 +0530 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240802_091634_260332_C5AE0DF1 X-CRM114-Status: GOOD ( 21.18 ) 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: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Catalin Marinas writes: > On Wed, Jul 31, 2024 at 09:26:31PM +0530, Aneesh Kumar K.V wrote: >> Aneesh Kumar K.V writes: >> > Will Deacon writes: >> >> On Wed, Jul 31, 2024 at 08:11:16PM +0530, Aneesh Kumar K.V wrote: >> >>> Will Deacon writes: >> >>> > diff --git a/drivers/firmware/smccc/kvm_guest.c b/drivers/firmware/smccc/kvm_guest.c >> >>> > index 89a68e7eeaa6..f3319be20b36 100644 >> >>> > --- a/drivers/firmware/smccc/kvm_guest.c >> >>> > +++ b/drivers/firmware/smccc/kvm_guest.c >> >>> > @@ -39,6 +39,8 @@ void __init kvm_init_hyp_services(void) >> >>> > >> >>> > pr_info("hypervisor services detected (0x%08lx 0x%08lx 0x%08lx 0x%08lx)\n", >> >>> > res.a3, res.a2, res.a1, res.a0); >> >>> > + >> >>> > + kvm_arch_init_hyp_services(); >> >>> > } >> >>> > >> >>> >> >>> That is a bit late to detect RMM? One of the requirements is to >> >>> figure out the pgprot_t flags for early_ioremap so that "earlycon" will >> >>> work (by mapping the address as shared alias). To do that we need to >> >>> make an RSI call to detect PROT_NS_SHARED mask as below. >> >>> >> >>> if (rsi_get_realm_config(&config)) >> >>> return; >> >>> prot_ns_shared = BIT(config.ipa_bits - 1); >> >> >> >> Why can't the earlycon MMIO address just have that high bit set? >> >> >> >> I think it's horribly fragile to try detecting all of this stuff before >> >> we're allowed to touch the console. We don't even bother with pKVM -- >> >> it's the guest firmware's responsibility to MMIO_GUARD the UART if it >> >> detects a debuggable payload. >> > >> > To mark something shared, we need to know the mask value which is >> > returned via rsi_get_realm_config() call. >> >> I guess you are suggesting to leave it to firmware to set up the device >> tree "reg-offset" with shared bit set? > > As you know, we've been through these options internally and we > concluded not to encode this information in the DT for various reasons. > I was trying to find out what a guest firmware-based control means. > > Personally I don't like this IPA split but that's too late to change it > now in the RMM spec. > Agreed. This also makes supporting both secure and non secure devices difficult. -aneesh