mirror of
https://github.com/LadybirdBrowser/ladybird.git
synced 2024-11-21 23:20:20 +00:00
Documentation: Remove another redundant chapter
Clearly nobody has used this in a while because cpuinfo.c for GCC 11 does not contain the code that's mentioned here.
This commit is contained in:
parent
d23d81d075
commit
2c392669c6
Notes:
sideshowbarker
2024-07-18 09:22:40 +09:00
Author: https://github.com/gunnarbeutner Commit: https://github.com/SerenityOS/serenity/commit/2c392669c6a Pull-request: https://github.com/SerenityOS/serenity/pull/8594 Reviewed-by: https://github.com/ADKaster Reviewed-by: https://github.com/awesomekling ✅ Reviewed-by: https://github.com/nico
1 changed files with 0 additions and 17 deletions
|
@ -58,23 +58,6 @@ To run SerenityOS in a WHPX-enabled QEMU VM:
|
|||
|
||||
### Known issues with WHPX
|
||||
|
||||
#### Illegal instruction on boot
|
||||
|
||||
Using `SERENITY_QEMU_CPU="max"` can trigger a QEMU bug where the OSXSAVE CPUID flag is erroneously set, playing havoc
|
||||
with feature detection logic in libgcc and resulting in this error.
|
||||
|
||||
To workaround this, first adjust the `SERENITY_QEMU_CPU` setting to emulate a more restricted feature set. `SERENITY_QEMU_CPU="qemu32"`
|
||||
appears to work in some cases, however in others causes the boot freeze issue above. It's worth playing around with
|
||||
various different values here to see if you can find one that works for you. Running `qemu-system-x86_64.exe -cpu ?` will
|
||||
list the supported CPU configurations.
|
||||
|
||||
If you cannot find a working CPU feature set, the next workaround is to patch libgcc in the Serenity toolchain build to
|
||||
remove the offending instruction.
|
||||
Comment out the `if ((ecx & bit_OSXSAVE))` block in `Toolchain/Tarballs/gcc-<version>/libgcc/config/i386/cpuinfo.c`. In
|
||||
GCC 10.2.0 this is lines 282-297.
|
||||
|
||||
Rebuild the toolchain using `Toolchain/BuildIt.sh` as normal, then rebuild Serenity.
|
||||
|
||||
#### Slow boot on HiDPI systems
|
||||
|
||||
On some Windows systems running with >100% scaling, the booting phase of Serenity might slow to a crawl. Changing the
|
||||
|
|
Loading…
Reference in a new issue