Go to file
Paolo Bonzini ba57bed537 smp: restore MSRs on S3 resume
Currently the MTRRs and MSR_IA32_FEATURE_CONTROL are not restored on S3
resume.  Because these have to be applied to all processors, SMP setup
has to be added to S3 resume.

There are two differences between the boot and resume paths.  First,
romfile_* is not usable in the resume paths so we separate out the
remaining common code to a new smp_scan function.  Second, smp_msr has
to be walked on the BSP as well, so we extract that out of handle_smp
and into a new function smp_write_msrs.  Then, resume can call
smp_write_msrs on the BSP followed by smp_scan to initialize the APs.

Reported-by: Laszlo Ersek <lersek@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
(cherry picked from commit 54e3a88609)
2016-07-13 09:49:00 +02:00
docs docs: Note v1.9.0 release 2015-11-17 09:19:18 -05:00
scripts build: fix .text section address alignment 2016-02-24 12:53:39 +01:00
src smp: restore MSRs on S3 resume 2016-07-13 09:49:00 +02:00
vgasrc build: Report gcc and binutils versions in debug log 2015-10-15 10:55:10 -04:00
.gitignore Start using Kconfig to configure SeaBIOS settings. 2011-01-29 09:44:33 -05:00
COPYING Initial checkin. 2008-02-25 22:25:15 -05:00
COPYING.LESSER Change license from GPLv3 to LGPLv3. 2009-01-15 20:52:58 -05:00
Makefile build: Report gcc and binutils versions in debug log 2015-10-15 10:55:10 -04:00
README Simplify README files - point to online documentation instead 2014-12-15 21:46:56 -05:00

README

Welcome to the SeaBIOS project!  This project implements an X86 legacy
bios that is built with standard GNU tools.

Please see build and developer information at:

  http://seabios.org/Developer_Documentation

For the impatient, SeaBIOS is built for QEMU and tested on QEMU with:

  make
  qemu -bios out/bios.bin

SeaBIOS can be configured with kconfig.  To change the default
configuration one can run "make menuconfig" prior to running "make".

For other types of builds, and for more detailed developer
documentation, please see the online documentation listed above.