From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 89C9BC43334 for ; Mon, 18 Jul 2022 15:07:28 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235098AbiGRPH0 (ORCPT ); Mon, 18 Jul 2022 11:07:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56232 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230427AbiGRPHZ (ORCPT ); Mon, 18 Jul 2022 11:07:25 -0400 Received: from mail.skyhub.de (mail.skyhub.de [5.9.137.197]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 92945252A2 for ; Mon, 18 Jul 2022 08:07:24 -0700 (PDT) Received: from zn.tnic (p200300ea972976d7329c23fffea6a903.dip0.t-ipconnect.de [IPv6:2003:ea:9729:76d7:329c:23ff:fea6:a903]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id 1434E1EC04DF; Mon, 18 Jul 2022 17:07:19 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1658156839; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=oGRc12uwCW6Zy2C3e0KwL/G5EXioGouDvvRrw6svDcc=; b=Cswe+hKCqyjxvev2BMGHOWXir+N2gI+0BSZztkVbTNyIn5cfy1RIdPZq12dO77obeDIcAn RIOwMGCRPdPHudk3rgQyhv/MmZIoXLU8QRSVZDLCSc3jwsPnNA18ye7IgJVjnHK6VDwKUo upD856RLOWof7pC+qaH32yh8GGSBudA= Date: Mon, 18 Jul 2022 17:07:14 +0200 From: Borislav Petkov To: Bharata B Rao Cc: 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> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jul 18, 2022 at 08:24:08PM +0530, Bharata B Rao wrote: > It may be a weird guest configuration, but it looks like > a kernel bug exposed by QEMU. I betcha you can generate a lot of "kernel bugs" with weird qemu options. If it is not a real use case, nobody cares. And even if it were a real use case, panicking the machine is not the right fix. -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette