Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp141076pxk; Wed, 9 Sep 2020 01:02:03 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyan1knhwwlMZ5iFs6Tpd50fSEv9gDBg74QW62v96gp4IJAcrIMt+aPck7hn9uqsrJTJNup X-Received: by 2002:a05:6402:1d0f:: with SMTP id dg15mr2975089edb.342.1599638523533; Wed, 09 Sep 2020 01:02:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1599638523; cv=none; d=google.com; s=arc-20160816; b=yLaccjyFL+BL5YHWmP4cN1iifPpln4aLZ3GUbHzF+gN1m1FtJoftg9T+sdz2g+mNfN AeDXJ4hwguFk2mc0hNeDDHygQHGbLbNgshBCQgT4s1fpumipdb3MaZT0tHRws6XsEUQ7 pgzD8UeVF4I2bk6MUvOkgccgXnPb/AbjgKt4hUYlFwPJanlyyMMRZPv7qt1JJL931col lgpAHWgl1W2n5zOcnqgLqPVSl8XIaWPj/mZ+zi0JtpgmrLH5ArtA6IyZImSDt8KWZgId inZwtvxRBYFDruoS9XX7In63pdtBachFLLwhkzofbBjsjsdjteI+lYSTLZsPWAnNuB6a UNNQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=wBquDOMvvGBMKlLoT0ZYSQBY2ltKHLixc0AqZwGUMEg=; b=WW4yr38k1WvOiYIbeHGzuE0f70bWz2Lui8AIs1iidScGVhrFjliMWR6R7bMu54tHcQ D73xZ0FixgLee+v1z7+jwtUyF3QW9hVBYA0StX5SoyPQn6//OG2jIQdXKLVenJ0z3J3a j5oDToFV2AuyHqTmQqqxi3U61tvqTpTuN+tRmvoD3bq2HKiq2/2TQ/XiZDWbUNDNlGb8 3WyazVlYxV2LwAyKTs0gGlqjOz1XaD8mEKnZNAgzTPl2cifYs9cXuW2DXvPgbBU94OON Ffi3Vr3mLjo1mfwSHg33CtL2imSSnlR340sDDF+aZvI95Rd2hnu9SZfIBznWFUSH4hO/ Ry1w== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=sLhlkDWQ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id i4si974459edt.298.2020.09.09.01.01.39; Wed, 09 Sep 2020 01:02:03 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=sLhlkDWQ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730079AbgIIIA1 (ORCPT + 99 others); Wed, 9 Sep 2020 04:00:27 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34092 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726642AbgIIIAZ (ORCPT ); Wed, 9 Sep 2020 04:00:25 -0400 Received: from mail-ed1-x541.google.com (mail-ed1-x541.google.com [IPv6:2a00:1450:4864:20::541]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0B3B1C061573 for ; Wed, 9 Sep 2020 01:00:25 -0700 (PDT) Received: by mail-ed1-x541.google.com with SMTP id b12so1645113edz.11 for ; Wed, 09 Sep 2020 01:00:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=wBquDOMvvGBMKlLoT0ZYSQBY2ltKHLixc0AqZwGUMEg=; b=sLhlkDWQlawJYdG6m+Rc4jQKtlkc+q3fCT1+NzbHo2HA4xyy9xzq+zUpBXekTZfHGi IqiS6LPRxDogwOfWRvTyrTCUsTWr/r5m20KxnDzu9p2cJM/5oZ+GhEbeMQu6CArbqsYs BCBbYDWoEXvjeQbVV5nUyqP80jdT/ukV5bArjBjiCpEMCVzXVpK7TB9ZEutccviygpxV VXUkbGsmn0q+UN1iB2OcB22gUDAwatS5xBeQ5O1f/9B8Ttrq2bDfqRVVjGLjYidRZ50S QTDjgJGKEj8h7rRohjKpViTmqORKxi6dID+T5y9GDYKUPW9Ze0k1JSzLAjHS7RQCuQXe So8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to; bh=wBquDOMvvGBMKlLoT0ZYSQBY2ltKHLixc0AqZwGUMEg=; b=o39s3LxOFXxST6sv8EUZrEkpHybU1c7CZiLN/Vkzj+NmQ9o7u6Ds61IVz0qVOHnonm lUzzqmdkXpymIveYQUV7LI3S4tigi35H3UiNQlDho4bqxomG4t9YgX0eT0pN+3VdvqFO dLP708VNiE6oMrGdahw2fGm2poZhGmTigeAG6TkZGMLcP8DjFPSa36CPRfpp3gx957DB g8GthAkCz1AnNjYGR8ZCetVMd6phlQ5zMqMXLPlU7K+LdJTL0o1nRnDTM+PzYUUJa1tf SEaPU6Km1xVuq0tLuK+P0LLgVr7Q7U+H3mDTW7ZDFb4N45cTsorRbDw4GDYWf2LH3y+w Sfkw== X-Gm-Message-State: AOAM530JpJW2Azzo+/+9lbX56iCD1kROKDTau1G2fvQ4FaQOP/0ggvir WtnlOpkWMFMMAztbXS1YCU4= X-Received: by 2002:a50:a693:: with SMTP id e19mr2753440edc.205.1599638423633; Wed, 09 Sep 2020 01:00:23 -0700 (PDT) Received: from gmail.com (54007801.dsl.pool.telekom.hu. [84.0.120.1]) by smtp.gmail.com with ESMTPSA id bz5sm1278231ejc.83.2020.09.09.01.00.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 09 Sep 2020 01:00:22 -0700 (PDT) Date: Wed, 9 Sep 2020 10:00:20 +0200 From: Ingo Molnar To: Andy Shevchenko , Masahiro Yamada , Arnaud Lacombe Cc: Thomas Gleixner , Ingo Molnar , Borislav Petkov , x86@kernel.org, "H. Peter Anvin" , linux-kernel@vger.kernel.org, Jarkko Nikula , Tony Luck Subject: Re: [PATCH v1] x86/defconfigs: Unbreak 32-bit defconfig builds Message-ID: <20200909080020.GA2437694@gmail.com> References: <20200908100018.50188-1-andriy.shevchenko@linux.intel.com> <20200908121354.GA3848343@gmail.com> <20200908134350.GX1891694@smile.fi.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200908134350.GX1891694@smile.fi.intel.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Andy Shevchenko wrote: > On Tue, Sep 08, 2020 at 02:13:54PM +0200, Ingo Molnar wrote: > > > > * Andy Shevchenko wrote: > > > > > After the commit 1d0e12fd3a84 ("x86/defconfigs: Refresh defconfig files") > > > 32-bit builds using defconfig become broken because on x86_64 build host > > > with no ARCH provided the default behaviour is to assume 64-bit independently > > > on the configuration file name. The crucial part is CONFIG_64BIT option > > > that used to be explicit. Let restore the latter option in order to unbreak > > > 32-bit builds. > > > > So exactly which build method broke due to this? The typical way to do a defconfig build is: > > > > make ARCH=i386 defconfig > > > > which still works fine AFAICS. > > uname => x86_64 > make i386_defconfig > > It was very convenient to not supply ARCH when build on multi-arch host. Nice, TIL about the extended 'make *config' targets. :-) Curiously, they aren't even mentioned in the 'configuration targets' section of 'make help' and are not discoverable unless you know their locations. Anyway, your fix makes sense now to me too. Do we need a similar for x86_64 defconfig, when built on 32-bit hosts? (not that anyone does that in practice, but just for completeness.) Also, it would be nice if there was a way to annotate the defconfig for 'make savedefconfig' preserved these ARCH choices - it currently strips out all non-enabled options that match their default configuration value. Thanks, Ingo