Incoming links: Microarchitecture
Bought: November 2023 during Black Friday sale for £1,323.00 to be Ciro Santilli's main personal laptop.
Six years after, and we are 2x on every key spec (except processor Hz ;-) at about 1/2 the price and 1/2 the weight (though smaller 14" screen for greater portability), so not bad! Customized to max out each hardware spec:
Specs:
- Processor: AMD Ryzen™ 7 PRO 7840U Processor (3.30 GHz up to 5.10 GHz)
- Operating System: No Operating Systemselected upgrade
- Operating System Language: No Operating System Languageselected upgrade
- Microsoft Productivity Software: None
- Memory: 64 GB LPDDR5X-6400MHz (Soldered)selected upgrade. Specs at: www.lenovo.com/gb/en/p/accessories-and-software/memory-and-storage/memory-and-storage-hard-drives/4xb1d04758 quotes "64 Gbps", i.e. 8 GB/s.
dd count=1M if=/dev/zero of=tmpgives only 255 MB/s however. - Solid State Drive: 2 TB SSD M.2 2280 PCIe Gen4 Performance TLC Opalselected upgrade
- Display: 14" WUXGA (1920 x 1200), IPS, Anti-Glare, Touch, 45%NTSC, 300 nits, 60Hz
- Graphic Card: Integrated GraphicsThe Ubuntu 23.10 "About system GUI describes its graphics as: Radeon 780M Graphics × 16, which e.g. www.techpowerup.com/gpu-specs/radeon-780m.c4020 documents as running the RDNA 3 microarchitecture.
- Camera: 1080P FHD RGB/IR Hybrid with Microphone
- Color: Thunder Black
- Factory Color Calibration: No Factory Color Calibration
- Wireless: Qualcomm Wi-Fi 6E NFA725A 2x2 AX & Bluetooth® 5.1 or above
- Integrated Mobile Broadband: No Wireless WAN
- Ethernet: Wired Ethernet
- Near Field Communication: No NFC
- Fingerprint Reader: Fingerprint Reader
- Keyboard: Black - English (EU)selected upgrade
- Battery: 4 Cell Li-Polymer 52.5Whselected upgrade
- Power Cord: 65W USB-C Slim 90% PCC 3pin AC Adapter - UKselected upgrade
- Electronic Privacy Filter: No ePrivacy Filter
- Adobe Elements: None
- Adobe Acrobat: None
- Adobe Creative Cloud: None
- Security Software: None
- Cloud Security Software: No Cloud Security Software
- Warranty: 3 Year Courier or Carry-in
Identifiers:
- Ethernet MAC address: fc:5c:ee:24:fb:b4
- Wi-Fi MAC address: 04:7b:cb:cc:1b:10
Upon arrival:
Buy research:
- www.phoronix.com/review/thinkpad-p14s-gen4 says Ubuntu running fine
- Intel vs amd: the Intel ones could come with a discrete rtx A500 GPU. GPU likely makes laptop heavier and less power efficient. And both have basically the same benchmark which is crazy:So the only downside is not being able to run CUDA.
- thought about Yoga or other Ultrabook options, but 2x price at same specs, so nah...
Log:
2024-01-17: firmware update:Actually fixed performance mode: askubuntu.com/questions/604720/setting-to-high-performance/1343879#1343879
Vendor: LENOVO
Version: R2FET36W (1.16 )
Release Date: 10/24/2023A computer is a highly layered system, and so you have to decide which layers you are the most interested in studying.
Although the layer are somewhat independent, they also sometimes interact, and when that happens it usually hurts your brain. E.g., if compilers were perfect, no one optimizing software would have to know anything about microarchitecture. But if you want to go hardcore enough, you might have to learn some lower layer.
It must also be said that like in any industry, certain layers are hidden in commercial secrecy mysteries making it harder to actually learn them. In computing, the lower level you go, the more closed source things tend to become.
But as you climb down into the abyss of low level hardcoreness, don't forget that making usefulness is more important than being hardcore: Figure 1. "xkcd 378: Real Programmers".
First, the most important thing you should know about this subject: cirosantilli.com/linux-kernel-module-cheat/should-you-waste-your-life-with-systems-programming
Here's a summary from low-level to high-level:
- semiconductor physical implementation this level is of course the most closed, but it is fun to try and peek into it from any openings given by commercials and academia:
- photolithography, and notably photomask design
- register transfer level
- interactive Verilator fun: Is it possible to do interactive user input and output simulation in VHDL or Verilog?
- more importantly, and much harder/maybe impossible with open source, would be to try and set up a open source standard cell library and supporting software to obtain power, performance and area estimates
- Are there good open source standard cell libraries to learn IC synthesis with EDA tools? on Quora
- the most open source ones are some initiatives targeting FPGAs, e.g. symbiflow.github.io/, www.clifford.at/icestorm/
- qflow is an initiative targeting actual integrated circuits
- microarchitecture: a good way to play with this is to try and run some minimal userland examples on gem5 userland simulation with logging, e.g. see on the Linux Kernel Module Cheat:This should be done at the same time as books/website/courses that explain the microarchitecture basics.
- instruction set architecture: a good approach to learn this is to manually write some userland assembly with assertions as done in the Linux Kernel Module Cheat e.g. at:
- github.com/cirosantilli/linux-kernel-module-cheat/blob/9b6552ab6c66cb14d531eff903c4e78f3561e9ca/userland/arch/x86_64/add.S
- cirosantilli.com/linux-kernel-module-cheat/x86-userland-assembly
- learn a bit about calling conventions, e.g. by calling C standard library functions from assembly:
- you can also try and understand what some simple C programs compile to. Things can get a bit hard though when
-O3is used. Some cute examples:
- executable file format, notably executable and Linkable Format. Particularly important is to understand the basics of:
- address relocation: How do linkers and address relocation work?
- position independent code: What is the -fPIE option for position-independent executables in GCC and ld?
- how to observe which symbols are present in object files, e.g.:
- how C++ uses name mangling What is the effect of extern "C" in C++?
- how C++ template instantiation can help reduce link time and size: Explicit template instantiation - when is it used?
- operating system. There are two ways to approach this:
- learn about the Linux kernel Linux kernel. A good starting point is to learn about its main interfaces. This is well shown at Linux Kernel Module Cheat:
- system calls
- write some system calls in
- pure assembly:
- C GCC inline assembly:
- write some system calls in
- learn about kernel modules and their interfaces. Notably, learn about to demystify special files such
/dev/randomand so on: - learn how to do a minimal Linux kernel disk image/boot to userland hello world: What is the smallest possible Linux implementation?
- learn how to GDB Step debug the Linux kernel itself. Once you know this, you will feel that "given enough patience, I could understand anything that I wanted about the kernel", and you can then proceed to not learn almost anything about it and carry on with your life
- system calls
- write your own (mini-) OS, or study a minimal educational OS, e.g. as in:
- learn about the Linux kernel Linux kernel. A good starting point is to learn about its main interfaces. This is well shown at Linux Kernel Module Cheat:
- programming language
