Date: Mon, 4 Mar 2013 12:56:56 +0100
When Kconfig was introduced in SeaBIOS with
commit a4c5daf0e2545361fadcad3015e10f8b23e53926
Author: Kevin O'Connor <kevin(a)koconnor.net>
Date: Mon Jan 24 22:13:58 2011 -0500
Initial commit of Kconfig build tool.
this typo was copied from Kconfig in Linux v2.6.38-rc2. In the meantime
Linux commit »kconfig: nconf: rewrite help texts« (0b616500) [1] rewrote
the texts for `nconf.c` – which might be ported too to SeaBIOS – and the
typo was fixed there. But it is still present in `mconf.c` as of Linux
3.8.
[1] http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=0…
---
tools/kconfig/mconf.c | 2 +-
tools/kconfig/nconf.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/kconfig/mconf.c b/tools/kconfig/mconf.c
index d433c7a..2a24c42 100644
--- a/tools/kconfig/mconf.c
+++ b/tools/kconfig/mconf.c
@@ -25,7 +25,7 @@
static const char mconf_readme[] = N_(
"Overview\n"
"--------\n"
-"This interface let you select features and parameters for the build.\n"
+"This interface lets you select features and parameters for the build.\n"
"Features can either be built-in, modularized, or ignored. Parameters\n"
"must be entered in as decimal or hexadecimal numbers or text.\n"
"\n"
diff --git a/tools/kconfig/nconf.c b/tools/kconfig/nconf.c
index db56377..bb797c9 100644
--- a/tools/kconfig/nconf.c
+++ b/tools/kconfig/nconf.c
@@ -15,7 +15,7 @@
static const char nconf_readme[] = N_(
"Overview\n"
"--------\n"
-"This interface let you select features and parameters for the build.\n"
+"This interface lets you select features and parameters for the build.\n"
"Features can either be built-in, modularized, or ignored. Parameters\n"
"must be entered in as decimal or hexadecimal numbers or text.\n"
"\n"
--
1.7.10.4
Changes from v1:
- Make CONFIG_CSM a top-level build target in parallel with COREBOOT/QEMU.
- More Kconfig cleanup.
- Add generic find_pmtimer() function to find the pmtimer from ACPI tables.
- Make Xen and coreboot builds both use find_pmtimer().
- Merge E820 table one entry at a time instead of wholesale copy.
- Add pic_save_mask() and pic_restore_mask() functions.
- Less intrusive size reduction for handle_post().
- Various other cleanups.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse(a)intel.com Intel Corporation
Hi,
> b44a7be17bdd270ea029a8e2ec0c2e80c6cd0444 virtio-scsi: Pack struct virtio_scsi_{req_cmd,resp_cmd}
> 5a7730db57ab0715223421e65b54fb50d6fefe5c virtio-scsi: Set _DRIVER_OK flag before scsi target scanning
> Anthony + Gerd, can we expect an rev to pc-bios/bios.bin soon to pick up
> these seabios changes for vhost-scsi..?
I don't feel like placing a seabios git snapshot into qemu.
I think we should just cherry-pick everything we need for qemu 1.5 into
the 1.7.2-stable branch, roll out a 1.7.2.2 release and put that into
qemu 1.5.
So, what will be needed?
(1) The two commits listed above.
(2) The patch for the pvpanic device (assuming it gets
merged for 1.5).
Anything else?
Hard freeze for qemu 1.5 is next Wednesday.
cheers,
Gerd
PS: For qemu 1.6 (which will hopefully include the acpi table
reorganization) we will need a new release from the master
branch and thus a bit more careful release planning.
Untested yet, but I thought I'd share the
BIOS bits so we can agree on direction.
In particular check out ROM sizes:
- Before patchset with DSDT enabled
Total size: 127880 Fixed: 59060 Free: 3192 (used 97.6% of 128KiB rom)
- Before patchset with DSDT disabled
Total size: 122844 Fixed: 58884 Free: 8228 (used 93.7% of 128KiB rom)
- After patchset:
Total size: 128776 Fixed: 59100 Free: 2296 (used 98.2% of 128KiB rom)
- Legacy disabled at build time:
Total size: 119836 Fixed: 58996 Free: 11236 (used 91.4% of 128KiB rom)
As can be seen from this, most size savings come
from dropping DSDT, but we do save a bit by removing
other tables. Of course the real reason to move tables to QEMU
is so that ACPI can better match hardware.
This patchset adds an option to move all code for formatting acpi tables
out of BIOS. With this, QEMU has full control over the table layout.
All tables are loaded from the new "/etc/acpi/" directory.
Any entries in this directory cause BIOS to disable
ACPI table generation completely.
A generic linker script, controlled by QEMU, is
loaded from "/etc/linker-script". It is used to
patch in table pointers and checksums.
BIOS still has limited ability to parse the tables,
for the following purposes:
- locate resume vector
- allocate RSDP in FSEG
- allocate FACS at an aligned address
--
MST
Michael S. Tsirkin (3):
linker: utility to patch in-memory ROM files
acpi: load and link tables from /etc/acpi/
acpi: add an option to disable builtin tables
Makefile | 2 +-
src/Kconfig | 12 +++++++-
src/acpi.c | 67 +++++++++++++++++++++++++++++++++++++++++++-
src/linker.c | 90 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
src/linker.h | 50 +++++++++++++++++++++++++++++++++
src/util.h | 1 +
6 files changed, 219 insertions(+), 3 deletions(-)
create mode 100644 src/linker.c
create mode 100644 src/linker.h
--
MST
The first patch cleans up some field assignments in build_madt(). The
second one handles the case when MADT is provided by qemu over fw_cfg.
I'll soon post the qemu-side series as well.
I cross-tested {patched, unpatched} qemu with {patched, unpatched}
seabios. Inside a RHEL-6 guest I dumped the RSDT, DSDT, and APIC (MADT)
in all four cases, and compared the results. Patched qemu with unpatched
seabios don't play nicely together (two APIC (MADT) tables present).
Otherwise everything seemed fine to me.
The CPU topology was set with
-smp 3,maxcpus=16,sockets=2,cores=4,threads=2
The table dumps / disassemblies are too big to include here, please find
them at <http://people.redhat.com/~lersek/acpi_move/madt_tests.tar.gz>.
Laszlo Ersek (2):
build_madt(): "fix" intsrcovr->{gsi,flags} and local_nmi->flags byte
order
accept MADT over fw_cfg
src/acpi.c | 31 +++++++++++++++++++++++--------
1 files changed, 23 insertions(+), 8 deletions(-)
Each time I boot seabios built with debug enabled,
I see this on serial console:
Scan for VGA option rom
WARNING! Found unaligned PCI rom (vd=1013:00b8)
Is this a bogus warning?
--
MST
On Mon, Apr 29, 2013 at 06:21:43PM +0300, Michael S. Tsirkin wrote:
> This will make it possible to use fw config
> info for pci initialization.
>
> Signed-off-by: Michael S. Tsirkin <mst(a)redhat.com>
> ---
> src/paravirt.c | 2 ++
> src/post.c | 1 -
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/src/paravirt.c b/src/paravirt.c
> index e5027d0..85aa423 100644
> --- a/src/paravirt.c
> +++ b/src/paravirt.c
> @@ -97,6 +97,8 @@ qemu_platform_setup(void)
> if (!CONFIG_QEMU)
> return;
>
> + qemu_cfg_init();
That wont work - the romfile stuff is needed earlier (eg, in
boot_init()).
-Kevin