Received: by 2002:ad5:4acb:0:0:0:0:0 with SMTP id n11csp4642726imw; Tue, 19 Jul 2022 10:21:01 -0700 (PDT) X-Google-Smtp-Source: AGRyM1vv8RZa3lWy/dTCUDEjpejumDUFXtttwANvwNOMQVyALyAx7yGCYOj/9RmHFhu+MunMIuTj X-Received: by 2002:a17:907:9693:b0:72f:9cc:63d7 with SMTP id hd19-20020a170907969300b0072f09cc63d7mr18131658ejc.661.1658251261465; Tue, 19 Jul 2022 10:21:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1658251261; cv=none; d=google.com; s=arc-20160816; b=WvGIKMMHXIVZMsqmGCD+bKB5Y1Y8Nner6gH7tRmUkXHIjaO2rEBRAwqWEFsyqA4t6/ 3fshMsOOY+OF0X/IM6uSXCJqlGbiTCuxJsJc7a9iKXYON0aE1eky+XO4rbbkipBO+9Ni 8XmglOLGVqLMUPgnVufg+evKOt6ywLB/UH5vbvmRANy2djDovOzCADZfGeIxAp89Bckf eUB8Rsmeg2tVTAX7iayfcf4VQG2IIMa4Mhm0GRqVhlZ1ZZQ+m8/D72x3PJGGUkSkSZDs sGUJQd5YatiUvnrjY3kp+dRD3sSdRJNI9yYc+IULEG6JeTmGCA0WCrKZIjSWFi6PT+0Q BkdQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=bul4f/ogPJoZ7GsIsEPnLV8s8aS6eNqTZiiR3CtFKmI=; b=zZ7+yEd2zM8JWztILhH2O4TZib3zXCUUcmc2JWis8RZtGnyD55DNoUPh6NE9BMO+Ci ZqWE3S3oCxc4rcUotmVQMO1RujPEeQb3i+2N54MyrgDLRdVoDxWgvvIu8mNuGKi/r734 AMO/kmZ3gFOjO6Qp3+zh0Bzlc6hL8i5SOLqRSkN71NHhk14qwcTnKOO8UCBGZhYku4cR WGqCTL1QVhriJMGCulnzSfCmu4yXcdQscskMzW6aGiFrQiQDMGbWBffWHU60MKpdjNF3 xYE9vLhmvjmBSnnXNayS8B0AIYC7fRb0LKfSIDoDkcI8DqQ9kqs/kvsG5YATQS/0ldbM Zx/g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=snT5Se+y; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id jt6-20020a170906dfc600b0072b36dc02dfsi17096934ejc.262.2022.07.19.10.20.35; Tue, 19 Jul 2022 10:21:01 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=snT5Se+y; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238343AbiGSRMr (ORCPT + 99 others); Tue, 19 Jul 2022 13:12:47 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38202 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238311AbiGSRMo (ORCPT ); Tue, 19 Jul 2022 13:12:44 -0400 Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 63E004F66B for ; Tue, 19 Jul 2022 10:12:43 -0700 (PDT) Received: by mail-pl1-x62b.google.com with SMTP id z3so177003plb.1 for ; Tue, 19 Jul 2022 10:12:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=bul4f/ogPJoZ7GsIsEPnLV8s8aS6eNqTZiiR3CtFKmI=; b=snT5Se+yuvdBC3zfM90TEFQsq1aLuAStrAnLKmhvGQIfSusy+bAUPqLvPfUN0F1ZHG MNf0p2TOgFgZAPJ+VMxT+2VoFFLi6BTHTtubFaHCyKwe/NcceTbD4XwjpeBGCg+TxhHj y2hEg5do6ERlc277ILrHKbmP9xSupIXEm9vY+3wbPAAfzr89BkjeZhxMopfoldjZZpWl 2kQ2HK0pQ7N5nC/veoIEkv9kzx2r73SFZ6soI5hI26zO/0hkeTx6VsyQesGReHtA5BPm Nj9L1MWpKIWRuPqXiFf61aEBxq/7br+dqrqT6mgbmNli8dDp1WlV34Z/O9fWTGE0ygfo v1Uw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=bul4f/ogPJoZ7GsIsEPnLV8s8aS6eNqTZiiR3CtFKmI=; b=iSrrXE0jNjRWyPj8y+0Yp48wFTzbDeSQCV7D61QW7NXC82P+fCBb77ACDZcbM62JfH 5ZSazNnxbwARLav5+7M4ldERp7iVg9ZoKcKZmDZhjfkMQTXEOd8UFkE6YYqVciyUVy6u 2E9zwnbvf98+rVgNavh4ZSjS78IoKaokk1w4OgjqRQwHyME1SqrlDpU5Y5VA49kEmdCi PWYFR3Nu720Q2VWoZqwJZ2YaWoOWoVL4VM2ZZgXfhYgdyyPH1gTBM9rOlgeT/55ih/Pw JoCwmU3PS/Xvn+hELCKEaq5NNKW47hMjSXSvHxQuRbU1B1Zx/1Q9n1NU5XmqQ1nP6S4c 5RCw== X-Gm-Message-State: AJIora8zP3k5NP0fbdvdIRgs6GfduNxco0Q4WDQLNGPCkPi710nurR20 weO+OwRQFyGs+AjI2+H89P1cRQ2gWuP83A== X-Received: by 2002:a17:902:7c88:b0:16c:e485:51b1 with SMTP id y8-20020a1709027c8800b0016ce48551b1mr15607543pll.34.1658250762727; Tue, 19 Jul 2022 10:12:42 -0700 (PDT) Received: from google.com (123.65.230.35.bc.googleusercontent.com. [35.230.65.123]) by smtp.gmail.com with ESMTPSA id a3-20020a1709027e4300b0016c500fb7bcsm5966504pln.140.2022.07.19.10.12.42 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 19 Jul 2022 10:12:42 -0700 (PDT) Date: Tue, 19 Jul 2022 17:12:38 +0000 From: Sean Christopherson To: Bharata B Rao Cc: Borislav Petkov , linux-kernel@vger.kernel.org, tglx@linutronix.de, mingo@redhat.com, x86@kernel.org, dave.hansen@linux.intel.com, nikunj@amd.com, hpa@zytor.com, Abraham.Shaju@amd.com Subject: Re: [RFC FIX PATCH] x86/e820: Stop kernel boot when RAM resource reservation fails Message-ID: References: <20220718085815.1943-1-bharata@amd.com> <24ccd22f-6708-3265-4012-66f01108ff22@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <24ccd22f-6708-3265-4012-66f01108ff22@amd.com> X-Spam-Status: No, score=-17.6 required=5.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF, ENV_AND_HDR_SPF_MATCH,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, USER_IN_DEF_DKIM_WL,USER_IN_DEF_SPF_WL autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 19, 2022, Bharata B Rao wrote: > On 7/18/2022 8:37 PM, Borislav Petkov wrote: > > > > I betcha you can generate a lot of "kernel bugs" with weird qemu > > options. If it is not a real use case, nobody cares. > > I see that we will hit this problem by default when starting > a guest with 1T or more memory using QEMU. That a user can create a bad configuration using QEMU's default MAXPHYADDR doesn't change the fact that adding memory beyond MAXPHYADDR is firmly a configuration bug. > > And even if it were a real use case, panicking the machine is not the > > right fix. > > I couldn't see a clean exit/recovery option in setup_arch()->e820__reserve_resources() > where this happens. Any suggestions? WARN or pr_err/warn() and move on, or just do nothing. Adding code to try and gracefully handle an architecturally impossible configuration is a waste of time and effort. Like Boris said, there's practically a limitless number of bad setups QEMU can create, this one just happens to be easier to create than others due to shortcomings in QEMU.