Language Selection

English French German Italian Portuguese Spanish

Intel and AMD in Linux: Intel Uncore Frequency, Per-Client Engine Busyness, Navi GPUs

Filed under
Linux
Hardware
  • Intel Uncore Frequency Driver On Linux Is Closer To Mainline With Latest Patches

    The Intel Uncore Frequency driver for Linux allows reading and setting the uncore frequency, which controls the RING / Last Level Cache (LLC) clocks. Increasing the uncore frequency can help with improving memory latency or at least making the latency consistent by avoiding the dynamic uncore frequency selection. Increasing the clocks obviously come with increased power/heat. By default, the Intel uncore frequency is dynamic based upon the CPU performance state and power constraints.

    Intel has long published as part of their data sheets that the uncore frequency is controlled via a specific MSR (register 0x620) while now the intel_uncore frequency driver makes it easy to read and manipulate it from user-space. Interested server administrators could already manipulate the MSR as desired, but the Intel Uncore Frequency Linux driver makes it very easy now to read and set via new sysfs interfaces.

  • Intel Revs Linux Patches For Per-Client Engine Busyness - Allowing For Great GPU Insight

    One of the set of patches for Intel's Linux kernel graphics driver that have been floating around for more than one year is about exposing per-client (process) statistics in how each application is making use of the GPU's render/blitter/video hardware and various insightful statistics related to that. The patches aren't queued for mainline yet but at least a new revision of the work was published.

  • RADV's Next-Gen Geometry Code Continues To Be Revised For Navi GPUs

    The NGG (Next-Gen Geometry) support with Navi continues to be refined by the open-source AMD Linux graphics drivers with the RADV Vulkan driver seeing a fresh batch of fixes/clean-ups, inspired in part by the NGG code from the RadeonSI and AMDVLK drivers.

    The latest batch of RADV NGG work comes via Valve open-source driver developer Samuel Pitoiset. Landing in Mesa 20.0-devel today is a performance optimization, support for the NGG passthrough mode, disabling of vertex grouping, and other tweaks.

    Nothing too major itself but the latest in a long series of NGG activity for the open-source AMD Linux graphics drivers.

More in Tux Machines

Meet the New Linux Distro Inspired by the iPad

I’ve seen a tonne of Linux distros come and go in the 12 years I’ve been blogging about Ubuntu, but precious few have been designed exclusively for tablet use. So when I came across JingOS, a new Ubuntu-based distro touting a touch-centric UI, I was naturally intrigued. Tablet-based Linux distros aren’t exactly common. JingOS’s developers say it is “the world’s first iPadOS-style Linux distro”. I don’t imagine anyone is going to take issue with that statement, especially once they’ve seen how it looks! Read more

Linus Torvalds Decides To Land NVIDIA RTX 30 "Ampere" Support In Linux 5.11

While new feature code is normally not allowed in past the end of the merge window for a given Linux kernel release cycle, Linus Torvalds has decided to merge the newly-published open-source driver code for the NVIDIA GeForce RTX 30 "Ampere" graphics cards for the Linux 5.11 kernel that will debut as stable in February. Ahead of this weekend's Linux 5.11-rc4 release, Linus Torvalds has merged the new initial open-source code for the NVIDIA RTX 30 / Ampere GPUs via the Nouveau driver. He was fine with allowing this late addition to Linux 5.11 as the new hardware support is all self-contained and doesn't risk regressing the existing NVIDIA GPU support within the Nouveau driver. Thus it's one of the rare times he permits new code to be added after a merge window since there is minimal risk of it regressing the status quo of hardware support. Read more

today's leftovers

  • Minimalist vs Modern - Linux Mint 20.1

    It's time to check out the two desktop environments built for the latest release of Linux Mint 20.1 - MATE and Cinnamon!

  • Google Docs Replacement | Self-Hosted 36

    Our favorite Google Docs killer with markdown support has a big update. We explain how we host it and why we love it.

  • Announcing Istio 1.8.2

    This release contains bug fixes to improve robustness. This release note describes what’s different between Istio 1.8.1 and Istio 1.8.2

  • openSUSE Tumbleweed – Review of the week 2021/02 – Dominique a.k.a. DimStar (Dim*)

    Dear Tumbleweed users and hackers, Somewhere, I read, 2021 will be the year of the Linux desktop. Do you agree? Let’s make it the year of Tumbleweed on the desktop. In any case, Tumbleweed has been steadily rolling with 5 snapshots published during this week (0107, 0108, 0110, 0111, and 0113).

  • Ubuntu 21.04 To Expand The Use Of Phased Package Updates - Phoronix

    With this spring's release of Ubuntu 21.04 there is more widespread use of "phased updates" for gradually rolling out new stable release updates to help avoid any regressions en masse from coming to light. For years the Ubuntu desktop has employed this phased updates strategy while now with it being plumbed into APT, Ubuntu Server and other versions will by default make use of phased updates. Going back a number of years in Ubuntu has been Phased Updates that wired into Update Manager has led to the gradual rollout of new stable release updates over a period of about two days. This has been done gradually to ensure that no regressions or potential big problems hit all Ubuntu users at once by over the course of many hours exposing more Ubuntu users to these updates.

Security Leftovers

  • Security updates for Friday

    Security updates have been issued by Debian (flatpak, ruby-redcarpet, and wavpack), Fedora (dia, mingw-openjpeg2, and openjpeg2), Mageia (awstats, bison, cairo, kernel, kernel-linus, krb5, nvidia-current, nvidia390, php, and thunderbird), openSUSE (cobbler, firefox, kernel, libzypp, zypper, nodejs10, nodejs12, and nodejs14), Scientific Linux (thunderbird), Slackware (wavpack), SUSE (kernel, nodejs8, open-iscsi, openldap2, php7, php72, php74, slurm_20_02, and thunderbird), and Ubuntu (ampache and linux, linux-hwe, linux-hwe-5.4, linux-hwe-5.8, linux-lts-xenial).

  • Project Zero: Introducing the In-the-Wild Series

    At Project Zero we often refer to our goal simply as “make 0-day hard”. Members of the team approach this challenge mainly through the lens of offensive security research. And while we experiment a lot with new targets and methodologies in order to remain at the forefront of the field, it is important that the team doesn’t stray too far from the current state of the art. One of our efforts in this regard is the tracking of publicly known cases of zero-day vulnerabilities. We use this information to guide the research. Unfortunately, public 0-day reports rarely include captured exploits, which could provide invaluable insight into exploitation techniques and design decisions made by real-world attackers. In addition, we believe there to be a gap in the security community’s ability to detect 0-day exploits.

  • Google series on in-the-wild exploits

    The Google Project Zero blog is carrying a six-part series exploring, in great detail, a set of sophisticated exploits discovered in the wild.