https://bugs.winehq.org/show_bug.cgi?id=52968
Bug ID: 52968 Summary: CPU BoostTester manages to run only on real cores in Windows, but not with wine Product: Wine Version: 7.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: christian.frank@gmx.de Distribution: ---
Hi,
the following tiny porgram is used to test the boost capability of cpus. It detects real cores and only tests those, not the smt siblings.
On windows it manages to run on the real cores only. On Linux it runs on the cores 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30
I am using a 5950x. The real cores are 0-15. The siblings ar 16-31. 0+16 is a pair, 1+17, 2+18 etc.. So instead of testing the 16 real cores, it is testing only 8 + siblings.
The software is availible here, including source. I don't know if the software is doing some strange things to detect the real cores or if the issue is on the wine side.
As the source is just a handful of c++ code, someone with experience might take a look and judge where the problem is, wine or the program.
Here is the link:
https://github.com/jedi95/BoostTester
Many thx !
https://bugs.winehq.org/show_bug.cgi?id=52968
Sveinar Søpler cybermax@dexter.no changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |cybermax@dexter.no
--- Comment #1 from Sveinar Søpler cybermax@dexter.no --- Interesting. Seems to be that way on I7 8700K aswell, doing core 0-2-4-6-8-10, and afaik my real cores are 0-1-2-3-4-5.
Using these two patches: https://github.com/ValveSoftware/wine/commit/ec795b741d316ae18ab68dc0b75b2df... https://github.com/ValveSoftware/wine/commit/5381caf1be5fb176f623ca96b3cd72f...
And setting "WINE_LOGICAL_CPUS_AS_CORES=1" makes this BoostTester run through all cores+threads, so guess it is some sort of detection thing from wine. Maybe the real/threads layout is different for various package types, and wine would need some sort of mechanic to get this from kernel (possibly not easily obtainable from userspace), or one would need a cpu-id thing for "most-popular-cpus" with a fallback to what it is now?
Not a solution to the issue, but atleast something to experiment with if you want to.
https://bugs.winehq.org/show_bug.cgi?id=52968
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, hardware, source URL| |https://github.com/jedi95/B | |oostTester