linux-kernel - Re: [PATCH] arm64: dts: renesas: r8a77951: Add reserved memory region

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAMuHMdW9dAxJwzD=W1xLN2e_T_BNFk5MfbWh24Btur-o+-n4sg@mail.gmail.com>
Date:   Mon, 14 Nov 2022 20:57:21 +0100
From:   Geert Uytterhoeven <geert@...ux-m68k.org>
To:     Detlev Casanova <detlev.casanova@...labora.com>
Cc:     linux-kernel@...r.kernel.org, Magnus Damm <magnus.damm@...il.com>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        "open list:ARM/RENESAS ARCHITECTURE" 
        <linux-renesas-soc@...r.kernel.org>,
        "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
        <devicetree@...r.kernel.org>
Subject: Re: [PATCH] arm64: dts: renesas: r8a77951: Add reserved memory region

Hi Detlev,

On Mon, Nov 14, 2022 at 8:48 PM Detlev Casanova
<detlev.casanova@...labora.com> wrote:
> The 0x3000000 bytes memory region starting at 0x54000000 is
> reserved for the lossy_decompression hardware that will try to
> decompress any data written in the region.
>
> Mark the region as no-map to prevent linux from using it as RAM.
>
> Signed-off-by: Detlev Casanova <detlev.casanova@...labora.com>

Thanks for your patch!

> --- a/arch/arm64/boot/dts/renesas/r8a77951.dtsi
> +++ b/arch/arm64/boot/dts/renesas/r8a77951.dtsi
> @@ -290,6 +290,18 @@ CPU_SLEEP_1: cpu-sleep-1 {
>                 };
>         };
>
> +       reserved-memory {
> +               #address-cells = <2>;
> +               #size-cells = <2>;
> +               ranges;
> +
> +               /* device specific region for Lossy Decompression */
> +               lossy_decompress: memory-region@...00000 {
> +                       no-map;
> +                       reg = <0x00000000 0x54000000 0x0 0x03000000>;
> +               };
> +       };

This depends on the firmware/boot loader stack.  If it configures a
Lossy Decompression region, it should make sure to pass this
info through the various boot loader components to Linux,
just like is already done with the memory regions, RPC-IF state,
and OpTee configuration.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds