[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <24ccd22f-6708-3265-4012-66f01108ff22@amd.com>
Date: Tue, 19 Jul 2022 09:45:31 +0530
From: Bharata B Rao <bharata@....com>
To: Borislav Petkov <bp@...en8.de>
Cc: linux-kernel@...r.kernel.org, tglx@...utronix.de, mingo@...hat.com,
x86@...nel.org, dave.hansen@...ux.intel.com, nikunj@....com,
hpa@...or.com, Abraham.Shaju@....com
Subject: Re: [RFC FIX PATCH] x86/e820: Stop kernel boot when RAM resource
reservation fails
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?
Regards,
Bharata.
Powered by blists - more mailing lists