From: "H. Peter Anvin" <hpa@zytor.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: devzero@web.de, linux-kernel@vger.kernel.org, Matt.Domsch@dell.com
Subject: Re: [PATCH] [RFC] be more verbose when probing EDD
Date: Fri, 21 Dec 2007 18:22:41 -0800 [thread overview]
Message-ID: <476C74F1.2070407@zytor.com> (raw)
In-Reply-To: <20071222015758.GC4477@one.firstfloor.org>
Andi Kleen wrote:
>> Those don't live in an area of memory which is hard-limited to 32K.
>
> Why not 64k?
>
Because the bootloader needs some memory in the same segment that it
controls. Furthermore, since there were some residual uses of the
0x9000 segment (now removed, but not all bootloaders could be easily
fixed), we were limited to about 40K for everything.
Unfortunately we already have the problem that some bootloaders (notably
LOADLIN and mknbi) hardcoded an arbitrary limit which was even smaller
than that (about 16K, which we're already pushing up against.)
> Ok, that's a different argument than before. Ok. Although it's
> only a few bytes.
>
> I would lobby for any message at least contain the suggestion to try
> edd=off. That could save users a lot of time.
The important thing is that there is a message before and after. The
rest can be dealt with by Google on in documentation. That's what the
patch currently in x86setup.git does.
-hpa
next prev parent reply other threads:[~2007-12-22 2:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-16 15:34 [PATCH] [RFC] be more verbose when probing EDD devzero
2007-12-16 17:34 ` Parag Warudkar
2007-12-16 18:17 ` H. Peter Anvin
2007-12-22 1:15 ` Andi Kleen
2007-12-22 1:48 ` H. Peter Anvin
2007-12-22 1:57 ` Andi Kleen
2007-12-22 2:22 ` H. Peter Anvin [this message]
2007-12-22 2:41 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2007-12-16 19:11 devzero
2007-12-16 19:59 ` Parag Warudkar
2007-12-16 20:18 ` Alan Cox
2007-12-17 23:25 ` Jan Engelhardt
2007-12-17 23:27 ` H. Peter Anvin
2007-12-18 0:10 ` Alan Cox
2007-12-18 0:22 ` H. Peter Anvin
2007-12-16 19:19 devzero
2007-12-16 21:04 devzero
2007-12-16 21:01 ` Alan Cox
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=476C74F1.2070407@zytor.com \
--to=hpa@zytor.com \
--cc=Matt.Domsch@dell.com \
--cc=andi@firstfloor.org \
--cc=devzero@web.de \
--cc=linux-kernel@vger.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