From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id DAF782D7A6; Tue, 19 Dec 2023 17:18:24 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="CDhmM2wW" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5BC7CC433C9; Tue, 19 Dec 2023 17:18:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1703006304; bh=Rbbi3bdXZpPeMfvZ8EXC5cjsGqmRUe5g0GaIMT4Ia+0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=CDhmM2wWIG/1DeafIJBUkpCGfcZshWLfuFWRfarG75sYFkd5gi9lryaZnOt3+n6nZ oCDbK4lJcdC896QpbEGLJ0Jv8e3tGTvC+8XdsyBs9WWC2E1X5+MvL4APdat9/cqBOY V7YuxuEZz2FfnOsAzcCaS9R9RRByJOrdzuKIVxXNGm1ah+VaazcKXmKPumTDAQtx7N eem5F2ne2mPJvuXEKLngJw5xXhkxS+NFGgr2XtRMiAaT8V09AfAUDJA4IbOEgXVj3c 8/6UGm04sOEoZT4XxHOhNkhJqchB0X9zUFLmbgf7bhpKyVgquMb7rpukI2cDohqGeG 8kJtuNDK3f9ow== Date: Tue, 19 Dec 2023 17:18:19 +0000 From: Conor Dooley To: Conor Dooley Cc: "Lad, Prabhakar" , Palmer Dabbelt , geert+renesas@glider.be, Atish Patra , Paul Walmsley , apatel@ventanamicro.com, alexghiti@rivosinc.com, Bjorn Topel , suagrfillet@gmail.com, jeeheng.sia@starfivetech.com, petrtesarik@huaweicloud.com, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org, prabhakar.mahadev-lad.rj@bp.renesas.com Subject: Re: [RFT 1/2] RISC-V: handle missing "no-map" properties for OpenSBI's PMP protected regions Message-ID: <20231219-fernlike-device-4d7186aa4deb@spud> References: <20230810-crewless-pampers-6f51aafb8cff@wendy> <20231206-precut-serotonin-2eecee4ab6af@spud> <20231207-buffalo-varmint-de843c8a12bb@wendy> Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Y0vuaG6s5+IsNzDE" Content-Disposition: inline In-Reply-To: <20231207-buffalo-varmint-de843c8a12bb@wendy> --Y0vuaG6s5+IsNzDE Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hey, On Thu, Dec 07, 2023 at 01:11:23PM +0000, Conor Dooley wrote: > On Thu, Dec 07, 2023 at 01:02:00PM +0000, Lad, Prabhakar wrote: > > On Wed, Dec 6, 2023 at 2:26=E2=80=AFPM Conor Dooley = wrote: > > > On Wed, Dec 06, 2023 at 04:52:11AM -0800, Palmer Dabbelt wrote: > > > > On Thu, 10 Aug 2023 02:07:10 PDT (-0700), Conor Dooley wrote: >=20 > > > > > I'm perfectly happy to drop this series though, if people general= ly are > > > > > of the opinion that this sort of firmware workaround is ill-advis= ed. > > > > > We are unaffected by it, so I certainly have no pressure to have > > > > > something working here. It's my desire not to be user-hostile that > > > > > motivated this patch. > > > > > > > > IIUC you guys and Reneas are the only ones who have hardware that m= ight be > > > > in a spot where users aren't able to update the firmware (ie, it's = out in > > > > production somewhere). > > > > > > I dunno if we can really keep thinking like that though. In terms of > > > people who have devicetrees in the kernel and stuff available in west= ern > > > catalog distribution, sure. > > > I don't think we can assume that that covers all users though, certai= nly > > > the syntacore folks pop up every now and then, and I sure hope that > > > Andes etc have larger customer bases than the in-kernel users would > > > suggest. > > > > > > > So I'm adding Geert, though he probably saw this > > > > months ago... > > > > > > Prabhakar might be a good call on that front. I'm not sure if the > > > Renesas stuff works on affected versions of OpenSBI though, guess it > > > depends on the sequencing of the support for the non-coherent stuff a= nd > > > when this bug was fixed. > > > > > ATM, I dont think there are any users who are using the upstream > > kernel + OpenSBI (apart from me and Geert!). Currently the customers > > are using the BSP releases. >=20 > That doesn't really answer whether or not you (and your customers) are > using an affected version of the vendor OpenSBI? > The affected range for OpenSBI itself is [v0.8 to v1.3). Did you perhaps miss this mail Prabhakar? Cheers, Conor. --Y0vuaG6s5+IsNzDE Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCZYHQWwAKCRB4tDGHoIJi 0qC/AQDhdNlr9kHILIKz2xZ2WYD3SYxAiUhSXQD5sQ628Xbt2wD+Ln3DFaA1ILE1 XDHWGjSnaEkAkeVg8Q8Dz5D/SwDYFAo= =Fz5n -----END PGP SIGNATURE----- --Y0vuaG6s5+IsNzDE--