Language Selection

English French German Italian Portuguese Spanish

AMD Zen 3 and Linux

Filed under
Linux
Hardware
  • AMD Zen 3 "Family 19h" Enablement Beginning With The Linux 5.6 Kernel

    With the upcoming Linux 5.6 kernel cycle will be the first of many patches to come surrounding AMD Zen 3 "Family 19h" support.

    So far there haven't been any AMD Family 19h patches to the Linux kernel besides k10temp driver support. But queued up ahead of the weekend were a couple changes relating to Zen3/19h beginning to collect in ras/core for the Linux 5.6 merge window kicking off in the next week or two.

  • AMD Zen 3 Microcode Spotted in the Linux Kernel

    AMD Zen 3 microcode has recently been spotted in the Linux kernel, months ahead of the expected launch of this new line of processors.

    The discovery was shared on Twitter by @KOMACHI_ENSAKA, who says the new code is linked with EDAC, or Error Detection and Correction.

    By the looks of things, the Linux kernel is updated to support the AMD Family 19h processors, which represents the new Zen 3-based chip family.

    As the leaker notes, AMD 17h series can still be used, as they’re already supported – Family 17h is the existing AMD Zen 2 series.

AMD Zen 3 Linux update suggests a radically different CPU design

  • AMD Zen 3 Linux update suggests a radically different CPU design to Zen 2

    The new Linux patch details support for Family 19h of AMD’s processor silicon, which is widely assumed to be a reference to the Zen 3 family given that the Family 17h refers to the current Zen 2 CPUs and APUs. As such this is definitely not the Linux code base getting prepped for the Ryzen 4000 APUs that have been launched at CES, but the Ryzen 4000 CPUs being launched, likely around Computex.

    Confusing? Nah, Ryzen 4000 chips are obviously not the same as Ryzen 4000 chips, that would be stupid. Anyways, the new Linux code doesn’t really give us any extra details about the new Zen 3 microarchitecture, beyond providing a pair of different Family 19h CPU device IDs. And those themselves tell us precious little aside from the fact there are AMD Zen 3 chips being prepped for testing.

AMD Includes Zen 3 Microcode In Linux Kernel

  • AMD Includes Zen 3 Microcode In Linux Kernel

    After the success of Zen 2 powered CPUs, Dr. Lisa Su, AMD’s CEO, formally disclosed in his recent interview that AMD is planning to release Zen 3 later this year.

    Additionally, famed Hardware leaker, Komachi Ensaka, also tweeted revealing the line of code added to the Linux kernel for the Family of 19h system, which is the family of AMD CPUs based on the Zen 3 microarchitecture.

AMD's next generation Zen 3 CPU code will be added to the Linux

  • AMD's next generation Zen 3 CPU code will be added to the Linux kernel before 2020 starts

    Aside from something unforeseen and catastrophic, Zen 3 is definitely making its debut this year. We know this because AMD managing director Dr. Lisa Su has already indicated this several times, including in an interview in which she promised that “Big Navi” (Navi 20) would also make its debut in 2020. If anyone needs more evidence on this matter, just turn their attention to the underlying code that is added to the Linux kernel.

    Interestingly, patches for the Linux kernel have been great in the past to point to new hardware before it officially launched. And more recently, updates to the Linux kernel have given references to things like Navi 22 and Navi 23, which are two unpublished Navi GPUs. Now Zen 3 is doing a cameo.

AMD Zen Thermal/Power Reporting Improvements...

  • AMD Zen Thermal/Power Reporting Improvements Could Hit Linux 5.6 But More Testing Needed

    Last week I eagerly reported on Ryzen CPUs on Linux finally seeing CCD temperatures and current/voltage reporting thanks to new patches to the k10temp driver by Google's Guenter Roeck who oversees the kernel's hardware monitoring "HWMON" subsystem. The patches seem to be working well and are tentatively queued in hwmon-next, but more testing is still needed.

AMD's next generation Zen 3 CPU

  • AMD's next generation Zen 3 CPU code will be added to the Linux kernel before 2020 starts

    Aside from something unforeseen and catastrophic, Zen 3 is definitely making its debut this year. We know this because AMD managing director Dr. Lisa Su has already indicated this several times, including in an interview in which she promised that “Big Navi” (Navi 20) would also make its debut in 2020. If anyone needs more evidence on this matter, just turn their attention to the underlying code that is added to the Linux kernel.

    Interestingly, patches for the Linux kernel have been great in the past to point to new hardware before it officially launched. And more recently, updates to the Linux kernel have given references to things like Navi 22 and Navi 23, which are two unpublished Navi GPUs. Now Zen 3 is doing a cameo.

  • Zen 3: AMD’s new architecture microcode surfaced in the Linux kernel

    Despite the fact that it only seems to be yesterday that the Zen 2 chips for the Ryzen 3000 processors were released, we have noted that the Zen 3 is on its way, which shouldn’t be too surprising considering that AMD does everything possible to keep its CPU line up to date every year.

AMD Zen 3 Linux Update To Feature A Very Different CPU Design

We may have just got a peek at AMD Zen 3

  • We may have just got a peek at AMD Zen 3 in this Linux kernel update

    References to Zen 3, the architecture of AMD’s next-gen Ryzen desktop processors, have turned up in the Linux kernel, hinting that these chips might just arrive sooner than we think.

    New versions of the Linux kernel are often combed through as they emerge, looking for clues like references to unreleased hardware, and this time around it’s Komachi_Ensaka (a prolific leaker) who spotted details of AMD’s ‘Family 19h’ processors, and shared them on Twitter.

AMD adds Zen 3 technology to the kernel of Linux

  • AMD ADDS ZEN 3 TECHNOLOGY TO THE KERNEL OF LINUX

    Although it may feel like just yesterday that the Zen2-powered chips came out in the Ryzen 3000-series cpus, we're already catching a lot of wind that Zen 3 is well on its way, which shouldn't be too surprising given that AMD is doing its best to keep its CPU lineup updated annually. Today, as spotted by hardware leaker Komachi, we caught a whiff of Zen 3 microcode being added to Linux kernel.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

NanoPi NEO3 Headless SBC Launched for $20 and up

Last month, we found out FriendlyELEC was working on NanoPi NEO3, a tiny SBC powered by Rockchip RK3328 processor and made for headless applications and networked storage thanks to Gigabit Ethernet and USB 3.0 ports, as well as a 26-pin GPIO header. At the time, the board was still been finalized, but the company has now started to take orders for $20 and up depending on options which include a cute white enclosure... [...] The Wiki has been updated as well, and the company provides both Ubuntu Core 18.04 based FriendlyCore, and OpenWrt based FriendlyWrt operating systems for the board with both relying on Linux 5.4.12 kernel. I’d also expect Armbian to eventually provide Ubuntu 20.04 and Debian 10 images. Read more

Moving (parts of) the Cling REPL in Clang

Motivation
===

Over the last decade we have developed an interactive, interpretative 
C++ (aka REPL) as part of the high-energy physics (HEP) data analysis 
project -- ROOT [1-2]. We invested a significant  effort to replace the 
CINT C++ interpreter with a newly implemented REPL based on llvm -- 
cling [3]. The cling infrastructure is a core component of the data 
analysis framework of ROOT and runs in production for approximately 5 
years.

Cling is also  a standalone tool, which has a growing community outside 
of our field. Cling’s user community includes users in finance, biology 
and in a few companies with proprietary software. For example, there is 
a xeus-cling jupyter kernel [4]. One of the major challenges we face to 
foster that community is  our cling-related patches in llvm and clang 
forks. The benefits of using the LLVM community standards for code 
reviews, release cycles and integration has been mentioned a number of 
times by our "external" users.

Last year we were awarded an NSF grant to improve cling's sustainability 
and make it a standalone tool. We thank the LLVM Foundation Board for 
supporting us with a non-binding letter of collaboration which was 
essential for getting this grant.


Background
===

Cling is a C++ interpreter built on top of clang and llvm. In a 
nutshell, it uses clang's incremental compilation facilities to process 
code chunk-by-chunk by assuming an ever-growing translation unit [5]. 
Then code is lowered into llvm IR and run by the llvm jit. Cling has 
implemented some language "extensions" such as execution statements on 
the global scope and error recovery. Cling is in the core of HEP -- it 
is heavily used during data analysis of exabytes of particle physics 
data coming from the Large Hadron Collider (LHC) and other particle 
physics experiments.


Plans
===

The project foresees three main directions -- move parts of cling 
upstream along with the clang and llvm features that enable them; extend 
and generalize the language interoperability layer around cling; and 
extend and generalize the OpenCL/CUDA support in cling. We are at the 
early stages of the project and this email intends to be an RFC for the 
first part -- upstreaming parts of cling. Please do share your thoughts 
on the rest, too.


Moving Parts of Cling Upstream
---

Over the years we have slowly moved some patches upstream. However we 
still have around 100 patches in the clang fork. Most of them are in the 
context of extending the incremental compilation support for clang. The 
incremental compilation poses some challenges in the clang 
infrastructure. For example, we need to tune CodeGen to work with 
multiple llvm::Module instances, and finalize per each 
end-of-translation unit (we have multiple of them). Other changes 
include small adjustments in the FileManager's caching mechanism, and 
bug fixes in the SourceManager (code which can be reached mostly from 
within our setup). One conclusion we can draw from our research is that 
the clang infrastructure fits amazingly well to something which was not 
its main use case. The grand total of our diffs against clang-9 is: `62 
files changed, 1294 insertions(+), 231 deletions(-)`. Cling is currently 
being upgraded from llvm-5 to llvm-9.

A major weakness of cling's infrastructure is that it does not work with 
the clang Action infrastructure due to the lack of an 
IncrementalAction.  A possible way forward would be to implement a 
clang::IncrementalAction as a starting point. This way we should be able 
to reduce the amount of setup necessary to use the incremental 
infrastructure in clang. However, this will be a bit of a testing 
challenge -- cling lives downstream and some of the new code may be 
impossible to pick straight away and use. Building a mainline example 
tool such as clang-repl which gives us a way to test that incremental 
case or repurpose the already existing clang-interpreter may  be able to 
address the issue. The major risk of the task is avoiding code in the 
clang mainline which is untested by its HEP production environment.
There are several other types of patches to the ROOT fork of Clang, 
including ones  in the context of performance,towards  C++ modules 
support (D41416), and storage (does not have a patch yet but has an open 
projects entry and somebody working on it). These patches can be 
considered in parallel independently on the rest.

Extend and Generalize the Language Interoperability Layer Around Cling
---

HEP has extensive experience with on-demand python interoperability 
using cppyy[6], which is built around the type information provided by 
cling. Unlike tools with custom parsers such as swig and sip and tools 
built on top of C-APIs such as boost.python and pybind11, cling can 
provide information about memory management patterns (eg refcounting) 
and instantiate templates on the fly.We feel that functionality may not 
be of general interest to the llvm community but we will prepare another 
RFC and send it here later on to gather feedback.


Extend and Generalize the OpenCL/CUDA Support in Cling
---

Cling can incrementally compile CUDA code [7-8] allowing easier set up 
and enabling some interesting use cases. There are a number of planned 
improvements including talking to HIP [9] and SYCL to support more 
hardware architectures.



The primary focus of our work is to upstreaming functionality required 
to build an incremental compiler and rework cling build against vanilla 
clang and llvm. The last two points are to give the scope of the work 
which we will be doing the next 2-3 years. We will send here RFCs for 
both of them to trigger technical discussion if there is interest in 
pursuing this direction.


Collaboration
===

Open source development nowadays relies on reviewers. LLVM is no 
different and we will probably disturb a good number of people in the 
community ;)We would like to invite anybody interested in joining our 
incremental C++ activities to our open every second week calls. 
Announcements will be done via google group: compiler-research-announce 
(https://groups.google.com/g/compiler-research-announce).



Many thanks!


David & Vassil

Read more Also: Cling C++ Interpreter Looking To Upstream More Code Into LLVM

This week in KDE: New features galore!

Tons and tons of awesome new features and UI polish landed this week, alongside an equally weighty ton of important bugfixes. Read more

Elive 3.8.14 beta released

The Elive Team is proud to announce the release of the beta version 3.8.14 This new version includes: Kernel updated to 5.6.14 retrowave special theme themes, designs, icons improvements and more customizations included bootup with a much more friendly graphical menu, it now remembers your last selected OS, all the options are in the same menu instead of submenus, disabled useless recovery options, improved resolution, fixed wallpaper issue on encrypted installations SWAP space is much more performant now, feedbacks welcome Read more