[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <877e0q3f68.fsf@nanos.tec.linutronix.de>
Date: Thu, 13 Feb 2020 12:22:23 +0100
From: Thomas Gleixner <tglx@...utronix.de>
To: Dan Williams <dan.j.williams@...el.com>, mingo@...hat.com
Cc: Dave Hansen <dave.hansen@...ux.intel.com>,
Andy Lutomirski <luto@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Borislav Petkov <bp@...en8.de>,
"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
Andrew Morton <akpm@...ux-foundation.org>,
David Hildenbrand <david@...hat.com>,
Michal Hocko <mhocko@...e.com>, vishal.l.verma@...el.com,
hch@....de, linux-kernel@...r.kernel.org,
linux-nvdimm@...ts.01.org, x86@...nel.org
Subject: Re: [PATCH v4 4/6] x86/mm: Introduce CONFIG_KEEP_NUMA
Dan Williams <dan.j.williams@...el.com> writes:
> +#ifdef CONFIG_KEEP_NUMA
> +#define __initdata_numa
> +#else
> +#define __initdata_numa __initdata
> +#endif
TBH, I find this conditional annotation mightingly confusing.
__initdata_numa still suggest that this is __initdata, just a different
section and some extra rules or whatever.
Something like __initdata_or_keepnuma (sorry I could not come up with
something prettier, but you get the idea.
Thanks,
tglx
Powered by blists - more mailing lists