From: Bharata B Rao <bharata@amd.com>
To: Boris Petkov <bp@alien8.de>, linux-kernel@vger.kernel.org
Cc: 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
Date: Mon, 18 Jul 2022 20:24:08 +0530 [thread overview]
Message-ID: <be498c32-bed6-d31a-ae94-6006dd59ea1e@amd.com> (raw)
In-Reply-To: <E7A3FF43-C49F-415E-81C6-CD14F4107349@alien8.de>
On 7/18/2022 4:12 PM, Boris Petkov wrote:
> On July 18, 2022 8:58:15 AM UTC, Bharata B Rao <bharata@amd.com> wrote:
>> Currently it is possible to start a guest with memory that
>> is beyond the addressable range of CPU. This can typically
>> be done by using QEMU without explicilty specifying the max
>> physical addressable bits (via phys-bits or host-phys-bits
>> options). In such cases QEMU will start the guest with more
>> than 1TB memory but would implicitly limit the phys-bits to 40.
>
> Why does the upstream kernel care about some weird qemu guest configurations?
It may be a weird guest configuration, but it looks like
a kernel bug exposed by QEMU.
Regards,
Bharata
next prev parent reply other threads:[~2022-07-18 14:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 8:58 [RFC FIX PATCH] x86/e820: Stop kernel boot when RAM resource reservation fails Bharata B Rao
2022-07-18 10:42 ` Boris Petkov
2022-07-18 14:54 ` Bharata B Rao [this message]
2022-07-18 15:07 ` Borislav Petkov
2022-07-19 4:15 ` Bharata B Rao
2022-07-19 17:12 ` Sean Christopherson
2022-08-04 9:46 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=be498c32-bed6-d31a-ae94-6006dd59ea1e@amd.com \
--to=bharata@amd.com \
--cc=Abraham.Shaju@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nikunj@amd.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox