From: "Andy Lutomirski" <luto@kernel.org>
To: "Michael Kelley" <mikelley@microsoft.com>,
"James Morris" <jmorris@namei.org>,
"Sasha Levin" <sashal@kernel.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Mike Rapoport" <rppt@linux.ibm.com>,
"Borislav Petkov" <bp@alien8.de>
Cc: "the arch/x86 maintainers" <x86@kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"James Morris" <James.Morris@microsoft.com>
Subject: Re: [GIT PULL] x86/urgent for v5.13-rc5
Date: Thu, 02 Mar 2023 08:14:06 -0800 [thread overview]
Message-ID: <51e60223-0d5d-428e-9126-2754020f19a1@app.fastmail.com> (raw)
In-Reply-To: <MWHPR21MB159330952629D36EEDE706B3D7379@MWHPR21MB1593.namprd21.prod.outlook.com>
On Tue, Jun 8, 2021, at 10:53 AM, Michael Kelley wrote:
> From: James Morris <jmorris@namei.org> Sent: Monday, June 7, 2021 11:47 AM
>>
>> On Sun, 6 Jun 2021, Sasha Levin wrote:
>>
>> > >
>> > >Let's see if Sasha can dig out something... CCed.
>> > >
>> > >@Sasha, can you figure out who we can talk to whether Windoze reserves
>> > >the first megabyte of memory unconditionally?
>> >
>> > That's a great question, but I can't help there anymore :)
>> >
>> > Adding James Morris...
>>
>> Adding Michael Kelley.
>>
>
> I checked with the Windows team. Peter Anvin's statement from 11
> years ago is true. On Intel and AMD processors, Windows unconditionally
> reserves the 1st megabyte of memory, minus one page used for real
> mode startup. This is done to work around BIOS bugs.
Sorry to dredge up old skeletons. Do you know *where* Windows allocates that one page used for real mode startup? The current code in Linux has some bugs allocating that page, and it would be nice to sort it out.
next prev parent reply other threads:[~2023-03-02 16:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 7:55 [GIT PULL] x86/urgent for v5.13-rc5 Borislav Petkov
2021-06-06 19:38 ` Linus Torvalds
2021-06-06 20:58 ` Mike Rapoport
2021-06-06 21:23 ` Linus Torvalds
2021-06-06 22:07 ` Borislav Petkov
2021-06-06 23:05 ` Sasha Levin
2021-06-07 18:46 ` James Morris
2021-06-08 17:53 ` Michael Kelley
2021-06-08 18:33 ` Borislav Petkov
2021-06-08 19:22 ` Linus Torvalds
2021-06-08 20:01 ` Borislav Petkov
2021-06-08 20:03 ` Linus Torvalds
2021-06-08 20:30 ` [PATCH] x86/setup: Document that Windows reserves the first MiB Borislav Petkov
2021-06-09 8:54 ` Mike Rapoport
2023-03-02 16:14 ` Andy Lutomirski [this message]
2023-03-02 21:17 ` [GIT PULL] x86/urgent for v5.13-rc5 Michael Kelley (LINUX)
2021-06-06 20:14 ` pr-tracker-bot
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=51e60223-0d5d-428e-9126-2754020f19a1@app.fastmail.com \
--to=luto@kernel.org \
--cc=James.Morris@microsoft.com \
--cc=bp@alien8.de \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=rppt@linux.ibm.com \
--cc=sashal@kernel.org \
--cc=torvalds@linux-foundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.