Except excavator and Zen are NOT in the menu.patch -p1 < zen.patch
patching file arch/x86/include/asm/module.h
Reversed (or previously applied) patch detected!
I'll try manual patching.
Code: Select all
gentoo-amd64 wrc # cd /usr/src/linux-4.10.1-gentoo
gentoo-amd64 linux-4.10.1-gentoo # patch -p1 < enable_additional_cpu_optimizations_for_gcc_v4.9+_kernel_v3.15+.patch
patching file arch/x86/include/asm/module.h
patching file arch/x86/Kconfig.cpu
patching file arch/x86/Makefile
patching file arch/x86/Makefile_32.cpu
gentoo-amd64 linux-4.10.1-gentoo #Code: Select all
gentoo-amd64 linux-4.9.11-gentoo # patch -p1 < enable_additional_cpu_optimizations_for_gcc_v4.9+_kernel_v3.15+.patch
patching file arch/x86/include/asm/module.h
Reversed (or previously applied) patch detected! Assume -R? [n]
Interesting. Does this have any advantage when compared to "nomal" CPU?NeddySeagoon wrote:That makes perfect sense.
Ryzen is like a NUMA system from the L3 cache up
Code: Select all
0100100100100000011000010110110100100000
0100111001100001010011100010000100100000
0100100100100000011000010110110100100000
0110000100100000011011010110000101101110
00100001the kernel is updated from ppaTony0945 wrote:I just realized something and looked it up.
Phoronix's tests are using Ubuntu 16.10 which is based on the 4.8 kernel and Ubuntu 17.04 which is based on 4.9
AFAIK, neither kernel has Ryzen support as such (i.e. just generic AMD) but does have Intel features.
A truer test would be, for example, the B350 Tomahawk board that he used with Gentoo with the 4.10.2 kernel, compiled with GCC 6.3 and march=native, compared to the Z170 Tomahawk running the same kernel, all compiled with march=native with the same compiler.
What began as a simple internal discussion about the validity of claims that Windows 10 scheduling might be to blame for some of Ryzen's performance oddities, and that an update from Microsoft and AMD might magically save us all, has turned into a full day with many people chipping in to help put together a great story. The team at PC Perspective believes strongly that the Windows 10 scheduler is not improperly assigning workloads to Ryzen processors because of a lack of architecture knowledge on the structure of the CPU.
In fact, though we are waiting for official comments we can attribute from AMD on the matter, I have been told from high knowledge individuals inside the company that even AMD does not believe the Windows 10 scheduler has anything at all to do with the problems they are investigating on gaming performance.
In the process, we did find a new source of information in our latency testing tool that clearly shows differentiation between Intel's architecture and AMD's Zen architecture for core to core communications. In this way at least, the CCX design of 8-core Ryzen CPUs appears to more closely emulate a 2-socket system. With that, it is possible for Windows to logically split the CCX modules via the Non-Uniform Memory Access (NUMA), but that would force everything not specifically coded to span NUMA nodes (all games, some media encoders, etc) to use only half of Ryzen. How does this new information affect our expectation of something like Naples that will depend on Infinity Fabric even more directly for AMD's enterprise play?
There is still much to learn and more to investigate as we find the secrets that this new AMD architecture has in store for us. We welcome your discussion, comments, and questions below!
CONFIG_X86_AMD_PLATFORM_DEVICE:
Select to interpret AMD specific ACPI device to platform device
such as I2C, UART, GPIO found on AMD Carrizo and later chipsets.
I2C and UART depend on COMMON_CLK to set clock. GPIO driver is
implemented under PINCTRL subsystem.
Symbol: X86_AMD_PLATFORM_DEVICE [=n]
Type : boolean
Prompt: AMD ACPI2Platform devices support
Location:
-> Processor type and features
Defined at arch/x86/Kconfig:585
Depends on: ACPI [=y]
Selects: COMMON_CLK [=y] && PINCTRL [=n]
This sounds to me that their SMT is working properly, but they haven't bothered explaining why people have been getting a NEGATIVE benefit with it turned on. The second paragraph is frankly a given item, it's just like saying there's clouds in the sky.AMD has also taken the time to address reports suggesting simultaneous multi-threading (SMT) was having a negative performance impact in some games. The company says they expect SMT to provide a "neutral/positive benefit", and quote a wide range of games where this behavior is seen.
AMD goes on to suggest that some game optimizations for Ryzen may be possible.
Sounds like corporate finger pointing to me.ct85711 wrote:As far as the scheduler in Windows 10 being an issue, I am uncertain of where to go on this, so I have been sitting on the sidelines. However, if my understanding on this is correct (from old reports), that the Windows 10 scheduler may have been causing performance issues. Combined with the current report saying Windows 10 isn't at fault, than it sounds to me Ryzen should be getting even better performance than they are right now and it's a on fault AMD for the missed extra performance. Either way, I don't know if I am correct on following this or not, hence why I am not holding this.
That would be very stupid. If Ryzen fails there will be no Zen+ there will be no AMD.Now that I think about it more about my earlier statement, then it sounds like AMD intentionally hobbled the cpu just so that the next one has an easy performance gain for little/no work involved.
From the comments section:LLVM 5.0 won't be released for about six months, but hopefully the scheduler will soon be introduced in mainline LLVM so it will be easier for interested individuals to try out and see how it impacts the AMD Ryzen performance. I'll certainly run some fresh AMD Ryzen compiler benchmarks when the code is updated -- for now see my current Ryzen GCC compiler tuning and GCC vs. Clang Ryzen benchmarks.
The Impact Of GCC Zen Compiler Tuning On AMD Ryzen Performance
Written by Michael Larabel in Software on 3 March 2017.
http://www.phoronix.com/scan.php?page=a ... ver1&num=1
Originally posted by Michael View Post
This LLVM article isn't about the kernel scheduler, rather the compiler scheduler model.
True but the problem here is people not recognizing that Ryzen as very new architecture. I would expect both operaing systems and compilers to show improved support over the next year. It is the way of the inustry since basically forever. Eventually support matures and we dont think About it any more.
What perplexes me though is who gets wound up over poor gaming performance. Especially on a processor that finally livesup to is billing. It seems like the negativity of the political world is spilling over into the world of AMD processors. Really guys we should be happy that Ryzen is doing so well against Intels crap. We need AMD!
As I understand hyperthreading, that result was guaranteed to happen somewhere. Some workloads benefit from the increased parallelism of SMT. Some workloads suffer because (at least in all the processors I have read about, which does not include Ryzen) splitting a core's processor into two hyperthreads does not give the same level of functionality as having two full independent cores. If the workload does not rely on the resources that are necessarily cannibalized to create that second virtual core, you get the benefit of a second thread with little or no penalty. If the workload needs those resources, you lose more than you gain back from the parallelism. If people are seeing performance drops in some games, that is unfortunate, but not unreasonable and not necessarily indicative of a problem in the hardware.ct85711 wrote:The main part I want to pick apart is this,This sounds to me that their SMT is working properly, but they haven't bothered explaining why people have been getting a NEGATIVE benefit with it turned on.AMD has also taken the time to address reports suggesting simultaneous multi-threading (SMT) was having a negative performance impact in some games. The company says they expect SMT to provide a "neutral/positive benefit", and quote a wide range of games where this behavior is seen.

http://wccftech.com/amd-ryzen-5-1600x-1 ... 11-launch/AMD Ryzen 5 Mainstream Processors Confirmed For April 11th Launch – 6 Core Ryzen 5 1600X To Cost $249, 4 Core Ryzen 5 1500X To Cost $189
http://wccftech.com/ryzen-fx-performanc ... um=related[Video] Ryzen From FX: Performance Gains Over Vishera
R5 1600X quite well. I will plan this upgrade.wrc1944 wrote:Some new info:http://wccftech.com/amd-ryzen-5-1600x-1 ... 11-launch/AMD Ryzen 5 Mainstream Processors Confirmed For April 11th Launch – 6 Core Ryzen 5 1600X To Cost $249, 4 Core Ryzen 5 1500X To Cost $189
http://wccftech.com/ryzen-fx-performanc ... um=related[Video] Ryzen From FX: Performance Gains Over Vishera
NeddySeagoon wrote:That makes perfect sense.
Ryzen is like a NUMA system from the L3 cache up
Theoretically, but you need a (device-tree?) setting to tell it how the nodes are configured.truekaiser wrote:So would setting the numa options in kernel help with performance?


"Your PC uses a processor that isn’t supported on this version of Windows" error when you scan or download Windows updates
https://support.microsoft.com/en-us/hel ... cessor-thaSymptoms
When you try to scan or download updates through Windows Update, you receive the following error message:
Unsupported Hardware
Your PC uses a processor that isn’t supported on this version of Windows and you won’t receive updates.
Additionally, you may see an error message on the Windows Update window that resembles the following:
Windows could not search for new updates
An error occurred while checking for new updates for your computer.
Error(s) found:
Code 80240037 Windows Update encountered an unknown error.
Cause
This error occurs because new processor generations require the latest Windows version for support. For example, Windows 10 is the only Windows version that is supported on the following processor generations:
Intel seventh (7th)-generation processors
AMD “Bristol Ridge”
Qualcomm “8996"
Because of how this support policy is implemented, Windows 8.1 and Windows 7 devices that have a seventh generation or a later generation processor may no longer be able to scan or download updates through Windows Update or Microsoft Update.
Resolution
We recommend that you upgrade Windows 8.1-based and Window 7-based computers to Windows 10 if those computers have a processor that is from any of the following generations:
Intel seventh (7th)-generation "Intel Core" processor or a later generation
AMD seventh (7th)-generation (“Bristol Ridge") processor or a later generation
Qualcomm “8996" processor or a later generation


I plan on keeping some settings and configs. But I am mostly aiming for a clean install as the fx8350 system was used for stuff i no longer do. Geared to vm's and emulation.wrc1944 wrote:truekaiser,
From my long-time amd systems experiences, plus a few things I've recently read on Ryzen, I'm virtually certain that any bulldozer and up to excavator am3+ system should at the very least boot right up on any of the new AM4/Ryzen systems hardware.
I also read somewhere that even even amd k8 systems would probably work. So, I'd think that what you're proposing would work, and I'd go even further to say that you might even consider just cloning over a full system partition image of your current fx8350 to the new nvme pciex4 root drive, and try booting into the new hardware with that. If you had boot and system on the same partition, it would seem to be pretty easy. However, I've never worked with SSD drives before, so maybe I'm missing something.

Code: Select all
emerge -e @system --keep-goingCode: Select all
emerge -e @worldCode: Select all
emerge -e @world --keep-goingflags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb cpb hw_pstate vmmcall bmi1 arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold