Graphics AiChengGongENGINEERING SIGNALS

TOPIC 03 / 08 · UAPI → GEM → ATOMIC KMS

Linux DRM / KMS

理解 DRM 子系统如何连接用户态驱动、内存对象、同步原语和原子显示提交。

01　用户态 UAPI
02　DRM Core
03　GPU Driver
04　Display Engine

核心组件

  • DRM Core
  • GEM
  • TTM
  • Atomic KMS
  • dma-buf
  • sync_file

关键接口

  • ioctl
  • dma-buf
  • fence
  • KMS properties

一帧的数据流

  1. 创建 GEM
  2. 导入/导出 dma-buf
  3. 提交 GPU
  4. 等待 fence
  5. Atomic Commit

调试入口

  • drm.debug
  • debugfs/dri
  • modetest
  • drm_info

阅读方法

先确认问题发生在哪一层，再沿接口检查所有权、缓冲区格式、同步与时序。动态条目只在证据和相关性达到公开阈值后出现。

RELATED SIGNALS

关联动态

60SCORE
发现来源LWN.net文章linux-drm / gpu-drivers

Twenty years of Pandoc ↗

摘要待补：<p>John MacFarlane has published a <a href="https://pandoc.org/twenty-years-of-pandoc.html">lengthy retrospective</a> to commemorate twenty years of the <a href="https://pandoc.org/">Pandoc</a> document converter.</p> <blockquote class="bq"> <p>On August 3, 2006, I uploaded the first version of pandoc to my website, releasing it under the free GPL license. Pandoc 0.1 consisted of about 3000 lines of Haskell code, with no dependencies aside from GHC's standard library. It could convert Markdown, reStructuredText, HTML, and LaTeX documents into any of these formats, plus RTF or S5. I had no idea at the time that this would just be the first of over two hundred releases over the next twenty years; that the project would become the <a href="https://github.com/EvanLi/Github-Ranking/blob/master/Top100/Haskell.md">most popular program written in Haskell</a>; that I would spend countless hours on bug-fixes, improvement, and project management; that I would collaborate with programmers in many other countries; that pandoc would come to support over fifty document formats; that it would allow automatic generation of citations and bibliographies; that it would become integrated into academic

查看原文 →
78SCORE
发现来源LWN.net文章linux-drm / gpu-drivers

C-Kermit 11 released ↗

摘要待补：For those of us with a long memory: John Goerzen has <a href="https://changelog.complete.org/archives/44456-celebrating-45-years-of-kermit-with-the-first-new-c-kermit-release-in-15-years-and-working-with-a-decades-old-c-codebase">announced</a> the release of C-Kermit&#160;11, the first release of this file-transfer utility in 15&#160;years. <p> <blockquote class="bq"> As Debian maintainer of Kermit, I noticed some areas where it wasn't matching modern expectations. One area was, not surprising for a project of its age, security. Another area was that its character set or line-ending conversions are usually not desired now; we are used to byte-identical binary transfers, and the defaults caused confusion and even some rare instances of data corruption. So I started making a few patches last year. </blockquote> <p> See <a href="https://github.com/OpenKermit/ckermit/releases/tag/v11.0.506">the changelog</a> for details on the work that has been done. <p> Most of us probably haven't thought about C-Kermit in years (if ever), but there was a time when it was an essential tool for moving files between machines.

查看原文 →
78SCORE
发现来源LWN.net文章linux-drm / gpu-drivers

SQLite Critical CVEs or LLM Slop? (JFrog blog) ↗

摘要待补：The JFrog blog <a href="https://research.jfrog.com/post/sqlite-critical-cves-or-llm-slops/">examines some reported vulnerabilities in SQLite</a>, some of which made their way into high-profile vulnerability databases, that turned out to be entirely fabricated by LLMs. <p> <blockquote class="bq"> These LLM slop CVEs can cause organizations to waste time investigating and patching vulnerabilities that do not actually exist, as well as polluting vulnerability databases. In environments where Critical vulnerabilities are automatically prioritized or tickets are opened based on vulnerability scores, such fabricated CVEs can turn into a real burden. <p> In environments where AI is used to automate vulnerability triage and remediation this becomes even more concerning. An AI agent that encounters a fabricated CVE may attempt to locate the vulnerable function, generate a patch, or recommend changes based on code that does not even exist. Instead of helping security teams remediate real vulnerabilities, it can lead them down a completely wrong path, potentially introducing unnecessary changes and wasting time. </blockquote> <p>

查看原文 →
68SCORE
发现来源Phoronix文章linux-drm / gpu-drivers / mesa-dri / wayland

Benchmarking Six Linux Distributions On The Framework Laptop 13 Pro ↗

摘要待补：With the new Framework Laptop 13 Pro now shipping powered by Intel Core Ultra Series 3 (Panther Lake) and a brand new hardware design, I have spent the past week testing out various Linux distributions on this very nice high-end laptop. All of the modern Linux distributions tested have been playing nicely with this new Panther Lake laptop. Of course, beyond testing for compatibility I also took the opportunity to run some Linux distribution performance benchmarks for this laptop powered by the flagship Core Ultra X9 388H.

查看原文 →
78SCORE
发现来源LWN.net文章linux-drm / gpu-drivers

Four stable kernels for Monday ↗

摘要待补：<p>Greg Kroah-Hartman has announced the release of the <a href="https://lwn.net/Articles/1086901/">7.1.6</a>, <a href="https://lwn.net/Articles/1086903/">6.18.42</a>, <a href="https://lwn.net/Articles/1086904/">6.12.101</a>, and <a href="https://lwn.net/Articles/1086905/">6.6.148</a> stable kernels. Each contains hundreds of patches&mdash;the 7.1.6 kernel has more than 700&mdash;with fixes throughout the tree. Users are advised to upgrade.</p> <p></p>

查看原文 →
78SCORE
发现来源LWN.net文章linux-drm / gpu-drivers

NetBSD 11.0 released ↗

摘要待补：<p>The release of <a href="https://netbsd.org/">NetBSD</a> 11.0, the 19th major version of the operating system, has been <a href="https://lwn.net/Articles/1086899/">announced</a>. There are many changes and enhancements since the 10.1 release, including a new port to RISC-V, better support for Linux system calls in <a href="https://man.netbsd.org/NetBSD-11.0/compat_linux.8"><tt>compat_linux()</tt></a>, as well as improvements to the <a href="https://man.netbsd.org/NetBSD-11.x-BRANCH/npf.7">NPF</a> firewall.</p> <blockquote class="bq"> <p>As you are probably aware, the number of security issues found or suspected everywhere has massively increased with the advent of AI tools. As a consequence, we can't publish a release without open issues. Instead of delaying the release further to fix them (new ones are being reported all the time), we've instead chosen to be transparent about this.</p> </blockquote> <p>See the full <a href="https://netbsd.org/releases/formal-11/NetBSD-11.0.html">release notes</a> for links to the binary distributions and links to the full change logs.</p> <p>

查看原文 →