From: Sasha Levin <sashal@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Mike Rapoport <rppt@linux.ibm.com>, x86-ml <x86@kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
James.Morris@microsoft.com
Subject: Re: [GIT PULL] x86/urgent for v5.13-rc5
Date: Sun, 6 Jun 2021 19:05:29 -0400 [thread overview]
Message-ID: <YL1UucKH0GfXddZo@sashalap> (raw)
In-Reply-To: <YL1HLdmh55uGAIs/@zn.tnic>
On Mon, Jun 07, 2021 at 12:07:58AM +0200, Borislav Petkov wrote:
>On Sun, Jun 06, 2021 at 02:23:21PM -0700, Linus Torvalds wrote:
>> On Sun, Jun 6, 2021 at 1:58 PM Mike Rapoport <rppt@linux.ibm.com> wrote:
>> >
>> > A while ago hpa said:
>> >
>> > As far as I know, Windows 7 actually reserves all memory below
>> > 1 MiB to avoid BIOS bugs.
>> >
>> > (https://bugzilla.kernel.org/show_bug.cgi?id=16661#c2)
>>
>> It would be good to have that checked somehow.
>>
>> I don't think this matters on any machine with gigs of RAM, but I do
>> wonder about the people who want to do small configurations. Maybe
>> they've given up on x86?
>>
>> It also eats into that somewhat precious legacy DMA resource and eats
>> up a fair chunk of that. Again, not an issue on modern hardware, but
>> ..
>>
>> > I believe that reserving everything below 1M after the real mode trampoline
>> > is allocated reduces amount of hidden dependencies and makes things simpler
>> > overall.
>>
>> Simpler, perhaps, and _I_ personally don't care about about 512kB of
>> memory any more on any machines I have, but ..
>
>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...
--
Thanks,
Sasha
next prev parent reply other threads:[~2021-06-06 23:05 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 [this message]
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 ` [GIT PULL] x86/urgent for v5.13-rc5 Andy Lutomirski
2023-03-02 21:17 ` 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=YL1UucKH0GfXddZo@sashalap \
--to=sashal@kernel.org \
--cc=James.Morris@microsoft.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rppt@linux.ibm.com \
--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.