[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHmME9q=Ymmot+c55uQGxy+ztc6ZMgiM0340RGF8wcE3D3TtvQ@mail.gmail.com>
Date: Mon, 30 Mar 2020 22:38:41 -0600
From: "Jason A. Donenfeld" <Jason@...c4.com>
To: Masahiro Yamada <masahiroy@...nel.org>
Cc: Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Borislav Petkov <bp@...en8.de>,
Peter Zijlstra <peterz@...radead.org>,
"H . Peter Anvin" <hpa@...or.com>, X86 ML <x86@...nel.org>,
clang-built-linux <clang-built-linux@...glegroups.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Al Viro <viro@...iv.linux.org.uk>,
Randy Dunlap <rdunlap@...radead.org>
Subject: Re: [PATCH v2 08/16] x86: replace arch macros from compiler with CONFIG_X86_{32,64}
On Mon, Mar 30, 2020 at 8:42 PM Masahiro Yamada <masahiroy@...nel.org> wrote:
>
> Also, I slightly prefer
>
> #if defined(CONFIG_X86_32) && !defined(CONFIG_UML)
>
> to
>
> #if defined(__i386__) && !defined(__arch_um__)
I would much prefer that too.
At some point it'd be nice to see this whole mess cleaned up with UML.
I've seen this a few places -- UML thinks its x86, except where it's
not, and then there are problems. For example, a lot of SIMD related
code has this.
Jason
Powered by blists - more mailing lists