linux/poky.git/meta/conf/machine/qemux86-64.conf, branch yocto-5.0.8

qemux86-64: Reduce tuning to core2-64

2023-01-11T11:03:34+00:00

Effectively revert "qemux86-64: build for x86-64-v3 (2013 Haswell and later) rather than Core 2 from 2006" (commit 6f2af1e5d1537b4d31e14946292bf58f0fd76fc9) Much as I'd love us to use the latest tuning, we do have some autobuilder hardware which isn't ready for this yet which breaks KVM and some qemu user mode usage as there appear to be TCG bugs too. I suspect we're not the only ones with such hardware. Drop the tune back to core2-64, anyone can easily customise it themselves if they need it. We can revisit this in a year or two as we should be ready then. It has beena good test of the rest of the support which all seems ready. I'd have preferred to use corei7-64 but that causes runqemu.RunqemuTests.test_boot_machine_iso to hang. Leave the newer tune file inclusion so people can change tunes more easily. (From OE-Core rev: 369b1dfa28b1791d45f068acc765190defecd460) Signed-off-by: Richard Purdie

qemux86-64: build for x86-64-v3 (2013 Haswell and later) rather than Core 2 from 2006

2023-01-06T12:03:46+00:00

This allows us to - test those more recent instruction sets (AVX, AVX2, BMI1, BMI2, F16C, FMA, LZCNT, MOVBE, XSAVE) - benefit from improved performance across the stack both in kvm-driven system emulation and when running on real silicon. For example, glibc: https://www.phoronix.com/news/Glibc-strcasecmp-AVX2-EVEX v4 level is adding AVX-512, which is far less established, particularly Intel has famously backtracked from supporting it in Alder Lake/Raport Lake client CPUs and AMD has only implemented it in very recent Zen4 products: https://www.phoronix.com/news/GCC-11-x86-64-Feature-Levels (From OE-Core rev: 6f2af1e5d1537b4d31e14946292bf58f0fd76fc9) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

qemux86-64: Allow higher tunes

2022-08-14T07:13:32+00:00

Back in 0be64e54a0e6 ("qemux86: Allow higher tunes") we moved the qemux86 machine to using the core-i7 tune file, for maximum flexibility and to allow for enabling advanced processor features if desired or required by various packagess, without changing the default tune. Do the same now for qemux86-64. Cc: Joshua Watt Cc: Richard Purdie (From OE-Core rev: a7411f5964f2e8384768b0a5e67817b3adc0ae8c) Signed-off-by: Tom Rini Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

mesa: PROVIDES virtual/libgles3

2021-12-14T22:46:38+00:00

It's assumed that not all OpenGL ES implementation are compliant with the 3.x specification. Therefore an additional virtual providers is created to explicit compatibility with OpenGL ES 3 specification. Cc: Quentin Schulz (From OE-Core rev: 405cd7a37988ced627fe6ad6fd3089c17f59367e) Signed-off-by: Quentin Schulz Signed-off-by: Richard Purdie

conf/machine: move tune files to architecture directories

2021-08-18T16:01:06+00:00

Move all of the tune files found in conf/machine/include into their respective architecture directories in that same location. All references to these will need to be updated. So, change the relevant ones for this tree in this commit as well. For the ARM tunes, nest them one further into armv8a, armv8m, etc. and rename some to make them uniform with the rest of the tunes. (From OE-Core rev: b6f15209bcfff953cce69da97a93f9ddff141ced) Signed-off-by: Jon Mason Signed-off-by: Richard Purdie

qemux86: drop resolution setting via uvesafb

2020-02-18T23:53:54+00:00

I am not sure if this has ever worked, but uvesafb is a really outdated (VBE from the 1990s), awkward (needs v86d) and limited (no support for high resolutions) way to do it. The specific reason 640x480-32 was introduced (ages ago) was to force 32 bit mode with vmware driver, as 16bit had rendering issues. The modern, supported option is video=... kernel parameter documented here: https://wiki.archlinux.org/index.php/kernel_mode_setting#Forcing_modes_and_EDID https://github.com/torvalds/linux/blob/master/Documentation/fb/modedb.rst which can be passed directly to runqemu and doesn't require special kernel modules. Sato under X will continue to use 640x480 as that is hardcoded into xorg.conf under qemu. (From OE-Core rev: 1cf26f69fd89b43be24cd1232c43e5050b9d718a) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

qemu: switch to '-vga std' emulated hardware from vmware/cirrus for x86/mips

2019-09-01T21:33:07+00:00

This is the qemu default since qemu 2.2, is generally supported better, and is recommended by upstream. It also has already been in use for arm/risc and ovmf. Additional information: https://bugzilla.yoctoproject.org/show_bug.cgi?id=13466 https://www.kraxel.org/blog/2014/10/qemu-using-cirrus-considered-harmful/ '-vga virtio' emulated hardware remains in use when virgl is enabled via a runqemu override. Also, adjust the error whitelist, as there is a number of new messages coming from the drivers that are not actual errors. (From OE-Core rev: 73cb104f3307736f4922f2e0c9648f9b2d3b3b6b) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

mesa: disable gallium swrast driver on x86 x32

2019-08-30T16:10:28+00:00

It was found to crash the X server on startup under qemu. (From OE-Core rev: 045011ed29c0ab45892ad0881a4a8987f2adc977) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

qemuboot-x86: move QB_SYSTEM_NAME to corresponding conf

2019-08-07T15:08:15+00:00

Configrations: MACHINE: qemux86-64 require conf/multilib.conf MULTILIBS = "multilib:lib32" DEFAULTTUNE_virtclass-multilib-lib32 = "x86" Reproduce steps: bitbake lib32-core-image-minimal runqemu qemux86-64 nographic lib32-core-image-minimal Errors: qemu cannot bootup since: Booting from ROM... This kernel requires an x86-64 CPU, but only detected an i686 CPU. Unable to boot - please use a kernel appropriate for your CPU. QEMU: Terminated For lib32 image, override has x86, so the qemubin set to qemu-system-i386, fix by move QB_SYSTEM_NAME to corresponding conf, don't use the override (From OE-Core rev: ffaf86f175b2e6caa3a0067f7b3725930b053715) Signed-off-by: Changqing Li Signed-off-by: Richard Purdie

machine: clean up config files

2019-04-01T13:48:44+00:00

Beautify the machine config files by making the names and descriptions more uniform and verbose (From OE-Core rev: 1108a24e2c58794163c8cf35154f8be5c1d06c29) Signed-off-by: Jon Mason Signed-off-by: Richard Purdie