linux-kernel - Re: [PATCH v5 1/4] sparc64: implement ioremap

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: <CAMuHMdUsKQPvOwxARcWMqmFB7BdatZe=3bR+BG=DCaq_yMfySw@mail.gmail.com>
Date:   Tue, 10 Dec 2019 09:08:42 +0100
From:   Geert Uytterhoeven <geert@...ux-m68k.org>
To:     Tuowen Zhao <ztuowen@...il.com>
Cc:     Lee Jones <lee.jones@...aro.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        Mika Westerberg <mika.westerberg@...ux.intel.com>,
        acelan.kao@...onical.com, "Luis R. Rodriguez" <mcgrof@...nel.org>,
        "David S. Miller" <davem@...emloft.net>,
        kbuild test robot <lkp@...el.com>,
        Christoph Hellwig <hch@....de>
Subject: Re: [PATCH v5 1/4] sparc64: implement ioremap_uc

On Thu, Oct 17, 2019 at 7:47 PM Tuowen Zhao <ztuowen@...il.com> wrote:
> On sparc64, the whole physical IO address space is accessible using
> physically addressed loads and stores. *_uc does nothing like the
> others.
>
> Cc: <stable@...r.kernel.org>
> Reported-by: kbuild test robot <lkp@...el.com>
> Signed-off-by: Tuowen Zhao <ztuowen@...il.com>
> ---
>  arch/sparc/include/asm/io_64.h | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/arch/sparc/include/asm/io_64.h b/arch/sparc/include/asm/io_64.h
> index 688911051b44..f4afa301954a 100644
> --- a/arch/sparc/include/asm/io_64.h
> +++ b/arch/sparc/include/asm/io_64.h
> @@ -407,6 +407,7 @@ static inline void __iomem *ioremap(unsigned long offset, unsigned long size)
>  }
>
>  #define ioremap_nocache(X,Y)           ioremap((X),(Y))
> +#define ioremap_uc(X,Y)                        ioremap((X),(Y))
>  #define ioremap_wc(X,Y)                        ioremap((X),(Y))
>  #define ioremap_wt(X,Y)                        ioremap((X),(Y))

Do we really need this? There is only one user of ioremap_uc(), which
Christoph is trying hard to get rid of, and the new devres helper that
triggers all of this :-(
https://lore.kernel.org/dri-devel/20191112105507.GA7122@lst.de/

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