::: AMD Zen Samlingstråd :::

Det har är inte trevligt alls. Jag kommer att avboka HERO kortet som jag har beställning på, frågan är bara vad ska man ta istället.

Efter att ha sett diskutioner om Windows 10 scheduler och att det behövs uppdateringar så gjorde jag en coreinfo dump själv, och vad jag kan se så är allt som det ska. Vet att jag fick några Windows updates igår.

C:\>coreinfo -c

Coreinfo v3.31 - Dump information on system CPU and memory topology
Copyright (C) 2008-2014 Mark Russinovich
Sysinternals - www.sysinternals.com

Logical to Physical Processor Map:
**--------------  Physical Processor 0 (Hyperthreaded)
--**------------  Physical Processor 1 (Hyperthreaded)
----**----------  Physical Processor 2 (Hyperthreaded)
------**--------  Physical Processor 3 (Hyperthreaded)
--------**------  Physical Processor 4 (Hyperthreaded)
----------**----  Physical Processor 5 (Hyperthreaded)
------------**--  Physical Processor 6 (Hyperthreaded)
--------------**  Physical Processor 7 (Hyperthreaded)

C:\>coreinfo -l

Coreinfo v3.31 - Dump information on system CPU and memory topology
Copyright (C) 2008-2014 Mark Russinovich
Sysinternals - www.sysinternals.com

Logical Processor to Cache Map:
**--------------  Data Cache          0, Level 1,   32 KB, Assoc   8, LineSize  64
**--------------  Instruction Cache   0, Level 1,   64 KB, Assoc   4, LineSize  64
**--------------  Unified Cache       0, Level 2,  512 KB, Assoc   8, LineSize  64
********--------  Unified Cache       1, Level 3,    8 MB, Assoc  16, LineSize  64
--**------------  Data Cache          1, Level 1,   32 KB, Assoc   8, LineSize  64
--**------------  Instruction Cache   1, Level 1,   64 KB, Assoc   4, LineSize  64
--**------------  Unified Cache       2, Level 2,  512 KB, Assoc   8, LineSize  64
----**----------  Data Cache          2, Level 1,   32 KB, Assoc   8, LineSize  64
----**----------  Instruction Cache   2, Level 1,   64 KB, Assoc   4, LineSize  64
----**----------  Unified Cache       3, Level 2,  512 KB, Assoc   8, LineSize  64
------**--------  Data Cache          3, Level 1,   32 KB, Assoc   8, LineSize  64
------**--------  Instruction Cache   3, Level 1,   64 KB, Assoc   4, LineSize  64
------**--------  Unified Cache       4, Level 2,  512 KB, Assoc   8, LineSize  64
--------**------  Data Cache          4, Level 1,   32 KB, Assoc   8, LineSize  64
--------**------  Instruction Cache   4, Level 1,   64 KB, Assoc   4, LineSize  64
--------**------  Unified Cache       5, Level 2,  512 KB, Assoc   8, LineSize  64
--------********  Unified Cache       6, Level 3,    8 MB, Assoc  16, LineSize  64
----------**----  Data Cache          5, Level 1,   32 KB, Assoc   8, LineSize  64
----------**----  Instruction Cache   5, Level 1,   64 KB, Assoc   4, LineSize  64
----------**----  Unified Cache       7, Level 2,  512 KB, Assoc   8, LineSize  64
------------**--  Data Cache          6, Level 1,   32 KB, Assoc   8, LineSize  64
------------**--  Instruction Cache   6, Level 1,   64 KB, Assoc   4, LineSize  64
------------**--  Unified Cache       8, Level 2,  512 KB, Assoc   8, LineSize  64
--------------**  Data Cache          7, Level 1,   32 KB, Assoc   8, LineSize  64
--------------**  Instruction Cache   7, Level 1,   64 KB, Assoc   4, LineSize  64
--------------**  Unified Cache       9, Level 2,  512 KB, Assoc   8, LineSize  64

@SectionX2: Inte på mitt heller.
Det är heldött.

Asus testat korten i snitt 12 sekunder innan launch?

@Yoshman: Just trådfördelning över CCX verkar lite lurigt precis som dom testar på anand, då dom kör 8+8 och håller dom separata i belastning så ökade prestandan ganska mycket (förutsatt belastning kunde delas i 8+8). När windows då pingpongar trådar mellan kluster så kommer det bli prestandatapp jämfört med att hålla tråden kvar inom samma kluster, också visat i tråden där.

http://i.imgur.com/72cbLFr.png
Grön stapel är enskild CCX användning på Ryzen

Många som testar draw calls på Ryzen med HLSL instancing från nVidia och tycker att det presterar skit men där har man lite samma problem, om jag på min 2600k forcerar HLSL att bara använda två fysiska kärnor (två trådar som används av programmet) så ökar min fps en smula (23->24fps, 1ship 16000 rocks, instancing off)), på Ryzen ökar det med praktiskt taget det dubbla när man forcerar till två fysiska kärnor inom samma kluster.

Frågan är då hur pass mycket som kan göras för att förbättra hur trådar fördelas över hårdvaran med ny mikrokod/uefi/drivare/winpatch?

Copy dism.exe, boot.wim & install.wim (sources directory) files from the Windows 7 ISO image to your hard-drive.
Download the USB driver for Ryzen: https://1drv.ms/u/s!Ag6oE4SOsCmDhGIQJdHdaXC-_w-C
Extract the package to the same directory as DISM is located.
Enter the folders containing the individual driver files and check that there is not "Unblock" button visible. If there is, you need to manually toggle it for each and every file.

- "DISM /mount-wim /wimfile:boot.wim /index:2 /mountdir:x:\xxx" (x:\xxx = a temporary path of your choice, make sure to have ~20GB of space available for install.wim).
- "DISM /image:x:\xxx /add-driver /driver:Ryzen_USB_W764\ /recurse /forceunsigned"
- "DISM /unmount-wim /mountdir:x:\xxx /commit"

Windows 7 install.wim files contain four different OS variants, regardless of the officially stated edition of the media you have (Home, Professional, Ultimate).
The index order within the install.wim is always the same, regardless of the edition: Index 1 = Home Basic, Index 2 = Home Premium, Index 3 = Professional, Index 4 = Ultimate.

So if your media is for Professional edition, you need to make the changes to Index 3. If it is a Ultimate media, then make the changes to Index 4, etc.

- "DISM /mount-wim /wimfile:install.wim /index:x /mountdir:x:\xxx" (x:\xxx = a temporary path of your choice, make sure to have ~20GB of space available for install.wim).
- "DISM /image:x:\xxx /add-driver /driver:Ryzen_USB_W764\ /recurse /forceunsigned"
- "DISM /unmount-wim /mountdir:x:\xxx /commit"

After you have added the drivers to both of the WIMs, you can install Windows 7 from a USB drive and using USB keyboard and mouse.
Make sure that you don't use USB ports provided by a 3rd party manufacturer (other than ASMedia), as there are still no drivers for those in the media.
After the installation, install the Relive chipset driver pack for Windows 7 (available at AMD.com).

I got Win7 installed, but I didn't do anything too fancy like slip streaming drivers to get it done. The key for me was having a PS2 keyboard and then having a PS2 mouse adapter. Well, I used a win7 DVD in an optical drive. That is also necessary.

My board is the Asus Prime B350-Plus. It only has one PS2 port so I had to do some shenanigans to get things done.

First have the DVD in the drive and the PS2 keyboard plugged in. Don't bother with a USB mouse because it won't work anyway. Boot from the DVD and you can do what you need with the keyboard to get windows installed. You have to remember certain keyboard tricks like using tab and arrow keys. Nothing hard, but most don't use these on a daily basis probably when you normally have a working mouse.
Do not put in a windows password. Leave that blank. This is critical for later.

After windows is installed I put the Asus driver DVD in. You get a popup about what to do and you can hit enter and get to the main menu, but there I was stuck. I couldn't get any keyboard tricks to work to move from the initial menu area to the driver area. Arrow keys and tab didn't do squat. I had to shut down and think about things a bit.

Now unplug the PS2 keyboard. Get the mouse PS2 to USB adapter. You plug that in the PS2 port and plug the mouse into it. The keyboard won't be plugged in or used for the next step.

Boot up, mouse only, and if you don't have a password it goes direct to the desktop. Now with the mouse you can navigate the driver disk menu and get the drivers installed. After installing and a reboot or two you are set. You can then put the keyboard and mouse both in how you want and they will work.

@Decimal: Om tråd 1 (på CCX 0) måste prata med tråd 2 (på CCX 1) blir det flaskhals