[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a3-jKEs+uGL=_kjmfzao6DYgmrkO+YWtNhv5O+hFw_qog@mail.gmail.com>
Date: Thu, 14 Jul 2022 10:24:49 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Xianting Tian <xianting.tian@...ux.alibaba.com>
Cc: Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
Alexandre Ghiti <alexandre.ghiti@...onical.com>,
Guo Ren <guoren@...nel.org>, Anup Patel <anup@...infault.org>,
Nick Kossifidis <mick@....forth.gr>,
Mike Rapoport <rppt@...nel.org>,
Heiko Stuebner <heiko@...ech.de>,
linux-riscv <linux-riscv@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
huanyi.xj@...baba-inc.com
Subject: Re: [PATCH V2 2/2] riscv: Add modules to virtual kernel memory layout dump
On Thu, Jul 14, 2022 at 4:59 AM Xianting Tian
<xianting.tian@...ux.alibaba.com> wrote:
>
> As MODULES is only defined for CONFIG_64BIT, so we dump it when
> CONFIG_64BIT.
Doesn't this cause a compile-time error on 32-bit?
> (unsigned long)VMEMMAP_END);
> print_ml("vmalloc", (unsigned long)VMALLOC_START,
> (unsigned long)VMALLOC_END);
> + if (IS_ENABLED(CONFIG_64BIT))
> + print_ml("modules", (unsigned long)MODULES_VADDR,
> + (unsigned long)MODULES_END);
The IS_ENABLED() check prevents the line from getting executed, but
unlike an #ifdef it still relies on it to be parsable.
Arnd
Powered by blists - more mailing lists