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;
Sender: Ingo Molnar <mingo.kernel.org@gmail.com>
Date:   Thu, 4 Aug 2022 11:46:35 +0200
From:   Ingo Molnar <mingo@kernel.org>
To:     Bharata B Rao <bharata@amd.com>
Cc:     Borislav Petkov <bp@alien8.de>, 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: <YuuVezQMK/ytzMTe@gmail.com>
References: <20220718085815.1943-1-bharata@amd.com>
 <E7A3FF43-C49F-415E-81C6-CD14F4107349@alien8.de>
 <be498c32-bed6-d31a-ae94-6006dd59ea1e@amd.com>
 <YtV3Ipvt96X/iO2J@zn.tnic>
 <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>
Precedence: bulk


* Bharata B Rao <bharata@amd.com> 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.
> 
> > 
> > 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?

I'd emit a low impact, non-fatal WARN()ing to make sure users aren't silent 
victims of an easily detectable firmware (Qemu) misconfiguration.

Thanks,

	Ingo