On Mon, 2013-02-11 at 19:31 +0200, Gleb Natapov wrote: > > When I began to tinker with OVMF, it supported one CPU only. > > > > After a while QemuInstallAcpiMadtTable() was added > > [AcpiPlatformDxe/Qemu.c] which grabs the number of CPUs via fw_cfg and > > installs an according MADT. This seemed to be enough to get several > > VCPUs recognized & working in a Linux guest.
That much is sufficient for the CSM case too, since the existing tables are simply passed on to the legacy OS. I've had various operating systems running in SMP mode quite happily. With the exception that they whine about the MTRRs, being inconsistent, of course :) > > When discussing related stuff internally @ RH, Gleb (CC'd) replied to me > > with the following (I hope you won't mind me quoting you here, Gleb; > > msgid <[email protected]>): > > > No, I won't mind of course. Also I will be glad if someone knowledgeable > will explain to me who does configuration, that is usually done by > firmware, on hot-plugged cpus? It's done by the kernel in that case. But it *doesn't* expect to have to do it at boot time; the firmware is supposed to do that. The kernel *will* do it, and will whine about it as you saw. So it would be good to fix the firmware... I could trivially enable the code in SeaBIOS that already does this, for the CSM case. But I don't *want* to, because that isn't where it should happen. -- dwmw2
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
