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: Mon, 1 Aug 2011 20:36:38 -0400 [thread overview]
Message-ID: <20110802003637.GA3046@morn.localdomain> (raw)
In-Reply-To: <8739hlb5t4.fsf@nemi.mork.no>
On Mon, Aug 01, 2011 at 03:49:11PM +0200, Bjørn Mork wrote:
> I just confirmed the issue running
>
> "JUNOS 11.1R3.5 built 2011-06-25 00:17:21 UTC"
>
> which is as new as it officially gets at the moment.
[...]
> Also confirmed that 11.1R3.5 is working with SeaBIOS modified as
> follows:
[...]
> - void *finaltable = malloc_high(structure_table_length);
> + void *finaltable = malloc_fseg(structure_table_length);
I'm not really sure how best to handle this. The smbios table can be
larger than the current space reserved for the f-segment (when there
are a large number of CPUs).
Some ideas:
There is actually space in the f-segment that is unused, but not given
to the malloc_fseg pool. That space could be given to the pool -
though the available space will still vary depending on the code size.
It's also possible to relocate the 32bit "run-time" code to high
memory which would then free up more space in the f-segment (at the
cost of some high memory being reserved from the OS). As above,
though, the f-segment is still fundamentally limited by the 16bit code
size.
Also, it's possible the code could try to use the f-segment if there
are less than say 16 cpus and use high memory when more cpus are
present.
-Kevin
next prev parent reply other threads:[~2011-08-02 0:36 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 [this message]
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
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=20110802003637.GA3046@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).