From: Kevin O'Connor <kevin@koconnor.net>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: Brandon Bennett <bennetb@gmail.com>,
seabios@seabios.org, qemu-devel@nongnu.org,
Sebastian Herbszt <herbszt@gmx.de>
Subject: Re: [Qemu-devel] [SeaBIOS] SeaBIOS error with Juniper FreeBSD kernel
Date: Wed, 3 Aug 2011 19:48:37 -0400 [thread overview]
Message-ID: <20110803234837.GA3596@morn.localdomain> (raw)
In-Reply-To: <87pqkm7jko.fsf@nemi.mork.no>
On Wed, Aug 03, 2011 at 02:42:15PM +0200, Bjørn Mork wrote:
>But what if additional data is added to
> the table, making f-segment allocation fail? Then you will end up with
> three different results depending on small changes instead of two:
>
> 1) nCPU <= 16 and f-segment allocation OK: SMBIOS in f-segment
> 2) nCPU > 16: SMBIOS in high mem
> 3) nCPU <= 16 and f-segment allocation failed: no SMBIOS table
If a reasonable limit is placed on the size of the SMBIOS table then
in practice the allocation will always succeed.
All of the f-segment allocations with the exception of the mptable are
small. The mptable allocation should probably have an upper bound
placed on it as well. There's currently 2048 bytes reserved for
malloc_fseg (CONFIG_MAX_BIOSTABLE), and the current smbios uses 263
bytes with one cpu and 938 bytes with 16 cpus (memory size may also
change size slightly).
-Kevin
prev parent reply other threads:[~2011-08-03 23:48 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-21 0:23 [Qemu-devel] SeaBIOS error with Juniper FreeBSD kernel Brandon Bennett
2010-02-21 4:05 ` Kevin O'Connor
2010-02-21 23:04 ` Brandon Bennett
2010-02-21 23:18 ` Brandon Bennett
2010-02-22 2:56 ` [Qemu-devel] SeaBIOS error with Nextstep bootloader Natalia Portillo
2010-02-28 19:51 ` Kevin O'Connor
2010-03-01 2:00 ` Natalia Portillo
2010-03-11 9:44 ` Natalia Portillo
2010-03-12 1:59 ` Kevin O'Connor
2010-03-12 9:05 ` Natalia Portillo
2010-03-13 6:30 ` Roy Tam
2010-03-13 14:42 ` [Qemu-devel] PS/2 mouse emulation problems Natalia Portillo
2010-03-13 14:44 ` [Qemu-devel] " Roy Tam
2010-03-13 20:23 ` Kevin O'Connor
2010-03-14 2:49 ` Roy Tam
2010-03-14 3:11 ` Roy Tam
2010-03-14 3:43 ` Kevin O'Connor
2010-03-14 5:28 ` Roy Tam
2010-03-14 7:11 ` Kevin O'Connor
2010-03-13 16:52 ` [Qemu-devel] SeaBIOS error with Nextstep bootloader Kevin O'Connor
2010-02-28 19:39 ` [Qemu-devel] SeaBIOS error with Juniper FreeBSD kernel Kevin O'Connor
2010-02-28 20:41 ` Gleb Natapov
2010-04-13 18:48 ` [Qemu-devel] " Bjørn Mork
2010-04-14 1:27 ` Kevin O'Connor
2010-04-14 10:51 ` Bjørn Mork
2011-07-07 15:45 ` [Qemu-devel] " Bjørn Mork
2011-07-07 23:50 ` Kevin O'Connor
2011-07-08 7:46 ` Bjørn Mork
2011-07-10 20:41 ` Kevin O'Connor
2011-07-10 21:25 ` [Qemu-devel] [SeaBIOS] " Sebastian Herbszt
2011-07-11 23:33 ` Brandon Bennett
2011-08-01 13:49 ` Bjørn Mork
2011-08-02 0:36 ` Kevin O'Connor
2011-08-02 9:33 ` Bjørn Mork
2011-08-02 12:41 ` Kevin O'Connor
2011-08-03 12:42 ` Bjørn Mork
2011-08-03 13:31 ` Avi Kivity
2011-08-03 13:48 ` Bjørn Mork
2011-08-03 14:03 ` Avi Kivity
2011-08-03 23:48 ` Kevin O'Connor [this message]
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=20110803234837.GA3596@morn.localdomain \
--to=kevin@koconnor.net \
--cc=bennetb@gmail.com \
--cc=bjorn@mork.no \
--cc=herbszt@gmx.de \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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;
as well as URLs for NNTP newsgroup(s).