From: Tom Rini Date: Wed, 22 Jul 2020 08:51:10 -0400 Subject: [PATCHv2] armv8: MMU: Mark code memory Executable, any other Non-Executable In-Reply-To: References: <20200619112409.27523-1-marek.bykowski@gmail.com> <20200619125332.27726-1-marek.bykowski@gmail.com> <20200718153400.GM6227@bill-the-cat> Message-ID: <20200722125110.GM6227@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Tue, Jul 21, 2020 at 02:33:03AM +0200, Marek wrote: > I'm on holidays right now, seeing the logs in my mobile I cannot infer much. > > What's the memory map after the patch? Intentional? I mean the > code/instruction region is read-only and executable and else read-write and > non-executable? > > May it happen that the tests try to write to instruction, read-only region? > If failures then than it is on purpose. > > If anything else needing a grater attention I'm sorry but it will have to > probably wait until I'm back from holidays, about two weeks from now. > > But thanks for looking through it. Our customers is keen on seeing the > change in the Upstream. > > I'm pretty sure we can work it out as all of the ARM SW suits, namely > arm-trusted-firmware and ARM Linux kernel are using the notion of > executable/non-executable and read-only/read-write. I think this will have to wait for you to return from holidays and investigate more. All I know is that the QEMU models are working as expected prior to the patch and fail with it. -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 659 bytes Desc: not available URL: