drivers/tty/hvc

Hypervisor Virtual Console (hvc) backends for PowerVM, z/VM, Xen, RISC-V, and ARM

A generic serial-style console layer that lets a Linux guest talk to its hypervisor or firmware instead of a physical UART. Backends cover IBM PowerVM and PowerNV partitions, IBM z/VM IUCV mainframe consoles, Xen guests, RISC-V SBI firmware consoles, and the ARM debug channel — how admins get a login prompt on virtualised or headless systems.

keep conf=0.81 deploy=medium replacement=none subsystem=tty category=virtualization
81%

recommendation

It should stay in the kernel because the underlying platforms are very much alive: IBM is still selling Power10 and Power11 systems in 2025 with PowerVM and HMC-based virtual terminals, z/VM and Xen guests continue to rely on it, and RISC-V SBI consoles are growing rather than shrinking. The code is also actively maintained, with stable-tree activity on hvc_console.c as recently as late 2025.

repository signals

16 files
8,118 source lines
71 commits, 5y
+731 / −465 lines added / removed, 5y
39 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 71 total · active in 33/61 months
2021 2022 2023 2024 2025 2026 2021-04: 0 commits · +0 −0 2021-05: 5 commits · +10 −12 2021-06: 1 commit · +0 −51 2021-07: 5 commits · +63 −37 2021-08: 0 commits · +0 −0 2021-09: 2 commits · +5 −8 2021-10: 4 commits · +59 −58 2021-11: 0 commits · +0 −0 2021-12: 1 commit · +27 −3 2022-01: 0 commits · +0 −0 2022-02: 0 commits · +0 −0 2022-03: 2 commits · +4 −2 2022-04: 4 commits · +216 −12 2022-05: 1 commit · +1 −1 2022-06: 0 commits · +0 −0 2022-07: 0 commits · +0 −0 2022-08: 1 commit · +1 −1 2022-09: 1 commit · +5 −6 2022-10: 1 commit · +1 −1 2022-11: 3 commits · +48 −21 2022-12: 1 commit · +2 −2 2023-01: 2 commits · +9 −9 2023-02: 6 commits · +34 −57 2023-03: 0 commits · +0 −0 2023-04: 0 commits · +0 −0 2023-05: 0 commits · +0 −0 2023-06: 0 commits · +0 −0 2023-07: 2 commits · +2 −3 2023-08: 4 commits · +19 −19 2023-09: 1 commit · +0 −2 2023-10: 3 commits · +28 −11 2023-11: 4 commits · +44 −27 2023-12: 2 commits · +83 −66 2024-01: 0 commits · +0 −0 2024-02: 2 commits · +10 −4 2024-03: 1 commit · +1 −1 2024-04: 0 commits · +0 −0 2024-05: 1 commit · +2 −13 2024-06: 0 commits · +0 −0 2024-07: 0 commits · +0 −0 2024-08: 0 commits · +0 −0 2024-09: 1 commit · +1 −1 2024-10: 0 commits · +0 −0 2024-11: 0 commits · +0 −0 2024-12: 1 commit · +1 −1 2025-01: 0 commits · +0 −0 2025-02: 1 commit · +4 −3 2025-03: 0 commits · +0 −0 2025-04: 0 commits · +0 −0 2025-05: 0 commits · +0 −0 2025-06: 0 commits · +0 −0 2025-07: 0 commits · +0 −0 2025-08: 1 commit · +3 −3 2025-09: 1 commit · +1 −1 2025-10: 0 commits · +0 −0 2025-11: 1 commit · +2 −3 2025-12: 0 commits · +0 −0 2026-01: 1 commit · +24 −5 2026-02: 3 commits · +20 −21 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. lore.kernel.org

    `drivers/tty/hvc/hvc_console.c` still received upstream/stable traffic in late 2025, indicating the subsystem is maintained rather than abandoned.

  2. ibm.com

    Current IBM Power10 documentation still describes HMC virtual terminal access for Linux logical partitions, which maps directly to active hvc use on modern Power systems.

  3. ibm.com

    IBM documentation references PowerVM deployments on Power9, Power10, and Power11 environments, showing the underlying virtualization platform remains current in 2025.

  4. ibm.com

    IBM support documentation updated in 2025 describes current vHMC offerings, reinforcing that PowerVM/HMC-based virtual-console environments are still being newly deployed.

codex reasoning notes (technical)

`drivers/tty/hvc` is a real driver directory: Kconfig/Makefile enumerate multiple hardware/firmware backends under the generic hypervisor virtual console layer. Lore evidence came from `mcp__lore_http__.lore_file_timeline` on `drivers/tty/hvc/hvc_console.c`, which returned late-2025 stable activity and a nontrivial 2021-2025 patch histogram. Deployment evidence came from web search results on IBM docs/support pages showing current PowerVM/HMC usage on Power10/Power11-era systems. I found no usable evidence of an upstream removal push in the successful queries; combined with ongoing maintenance and still-current host platforms, this points to keep rather than deprecate.