Hyeonggon Yoo
Posts
476Following
91Followers
93- Linux Kernel Developer @ Oracle (Linux Kernel MM) (2025.02 ~ Present)
- Ex-Intern @ SK Hynix (Linux Kernel MM) (2024.12 ~ 2025.01)
- Ex-Intern @ NVIDIA Korea (Security System Software) (2024.06 ~ 2024.11)
- Ex-Intern @ Panmneisa (CXL emulation stuff) (2023.09 ~ 2023.12)
- Undergraduate majoring CSE (estimated graduation: Feb. 2025)
- Working as reviewer at Linux Slab subsystem
- Born in August 6, 2000
Opinions are my own.
My interests are:
Memory Management,
Computer Architecture,
Circuit Design,
Virtualization
Hyeonggon Yoo
hyeyoo
Edited 1 year ago
In the ACPI specification; the character representing ACPI root namespace ('\') seems to be escaped (' and \') and looks like this.
How have people been reading this?
How have people been reading this?
0
0
1
Hyeonggon Yoo
hyeyoo
Edited 1 year ago
my keyboard is not responding until the kerenel is loaded. what's wrong I want uefi please
0
0
1
Hyeonggon Yoo
hyeyoo
Edited 1 year ago
UEFI (Unified Extensible Firmware Interface) standard defines the interface between platform firmware and OS (loader). UEFI only standards the interface with the firmware, but its implementation follows the Platform Integration (PI) standard, not UEFI. UEFI completely replaces BIOS used in traditional IBM PC environments.
An OS loader reads information such as ACPI tables, memory maps, etc. through UEFI and passes it to OS, which then takes over control. Most of the services provided by UEFI, including the ACPI Table and Memory Map, are not accessible after OS loader calls the UEFI's Boot Service ExitBootServices().
Intel provides open source reference implementations of firmware that adhere to the UEFI standard called EDK 2. The firmware also implements PCI host bus controllers, bus drivers, and device drivers.
In order to add CXL memory to the memory map during system initialization, the firmware must have CXL support added so that you can set up a CXL host bridge, switch, and device at system initialization before OS has taken the control.
An OS loader reads information such as ACPI tables, memory maps, etc. through UEFI and passes it to OS, which then takes over control. Most of the services provided by UEFI, including the ACPI Table and Memory Map, are not accessible after OS loader calls the UEFI's Boot Service ExitBootServices().
Intel provides open source reference implementations of firmware that adhere to the UEFI standard called EDK 2. The firmware also implements PCI host bus controllers, bus drivers, and device drivers.
In order to add CXL memory to the memory map during system initialization, the firmware must have CXL support added so that you can set up a CXL host bridge, switch, and device at system initialization before OS has taken the control.
0
0
1
Hyeonggon Yoo
hyeyoo
Edited 1 year ago
In ACPI-compatible OS environment, NUMA node of memory ranges and distance matrix between NUMA nodes are parsed from ACPI SRAT/SLIT tables and they are provided firmware.
ACPI HMAT describes latency/bandwidth characteristics.
CDAT is a set of registers in CXL that reports bandwidth/latency characteristics of CXL devices/switches. it is consumed by firmware to produce HMAT/SRAT tables.
ACPI HMAT describes latency/bandwidth characteristics.
CDAT is a set of registers in CXL that reports bandwidth/latency characteristics of CXL devices/switches. it is consumed by firmware to produce HMAT/SRAT tables.
0
0
1
Hyeonggon Yoo
repeated
repeated
AkaSci 🛰️
AkaSci@fosstodon.org
Edited 1 year ago
NASA is sending a software update to the Voyager 2 spacecraft today!
Data will be sent at 16 bps with a 19 kW transmitter using the 70-m dish at DSN Canberra.
Distance: 20 billion km
Light travel time: 18:40 hours
The patch contains logic to recover from glitches similar to the one in May 2022, when the AACS system on Voyager 1 was sending garbled data. The root cause was not diagnosed. The patch will be activated on Oct 28. Voyager 2 will be next.
https://www.jpl.nasa.gov/news/nasas-voyager-team-focuses-on-software-patch-thrusters
#Voyager
1/n
2
19
2
Hyeonggon Yoo
hyeyoo
0
0
3
Hyeonggon Yoo
hyeyoo
0
0
2
Hyeonggon Yoo
hyeyoo
Edited 1 year ago
https://coverage.kerneltesting.org/slab-experimental-6283c415/mm/
This is a merged LCOV output of my mm & slab test coverage from 30 different kernel configurations.
Looks mostly fine but there are a few small problems:
- Sometimes numbers are inconsistent
- Omission of (some) inline function coverage
This is a merged LCOV output of my mm & slab test coverage from 30 different kernel configurations.
Looks mostly fine but there are a few small problems:
- Sometimes numbers are inconsistent
- Omission of (some) inline function coverage
0
0
1