3 ms·
Proposal: Add bare metal support to Go
- Someone 2y agoFTA: // printk emits a single 8-bit character to standard output // //go:linkname printk runtime.printk func printk(c byte) So, printing “Hello, world!”, necessarily will have to make 13 calls to this function. I think I would have required a printk that prints an array of bytes. I expect that can be significantly faster on lots of hardware. In contrast, there’s // getRandomData generates len(b) random bytes and writes them into b // //go:linkname getRandomData runtime.getRandomData func getRandomData(b []byte) Here, they seem to acknowledge that it can be faster to make a single call.
- jeroenhd 2y agoThe method for printing uses an Intel UART driver to print characters. AFAIK, the standard low level UART generally only does single character transfers unless you write a (relatively) complex driver. Rendering per string is better per string, but I'm not so sure how bad the difference is when it comes to UART but I doubt the system has enough throughput for the first implementation to matter.
- 90s_dev 2y agoI wonder if this is related to that bare metal bios os post from a week or so ago. I asked the author why he used tty asm calls to print instead of calling int 10 directly and he said it was more efficient, but for different reasons. https://news.ycombinator.com/item?id=43873822 https://news.ycombinator.com/item?id=43873822
- Someone 2y ago> The method for printing uses an Intel UART driver to print characters The spec (rightfully) says “(e.g. serial console)”, not “Intel UART driver”. You cannot know what bare metal you’re running on. On some hardware it could be sending data out over Bluetooth, USB or WiFi because that’s the only connection to the outside world.
- ronsor 2y agoArguably `printk(c byte)` should be `printck(c byte)`, and there should be a separate `printk(s []byte)` that handles an array of bytes. If `printk` isn't implemented, then fall back to repeated calls of `printck`.
- lcarsip 2y agoprintk is the low level primitive for stdout printing and it's done this way as low level drivers generally only accept single characters. There are upper level functions which simply takes a []byte and make fmt.Printf() work seamlessly and effectively when not printing on an UART that only takes a single character as output. In TamaGo stdout is primarily used for debugging.
- timewizard 2y ago> Here, they seem to acknowledge that it can be faster to make a single call. It calls the internal Fill function to fill 4 bytes of the slice at a time. That calls the rng assembly stub function which uses 'rdrand' to get 32bits of random data. Which gets called len(b)/4 times. I don't think they did it for speed but rather to be more idiomatic. Anyways, OSDev has had a "Go Bare Bones" page for quite a while: https://wiki.osdev.org/Go_Bare_Bones https://wiki.osdev.org/Go_Bare_Bones
- jasonthorsness 2y agoWe use 'scratch' containers for many of our Go applications, so they have no user-space stuff other than our application binary. It reduces exposure for security vulnerabilities. This proposal seems to be taking that approach to the extreme - not even a kernel. Super-interesting; I wonder if it could run on cloud VMs? How tiny could the image become?
- jasonthorsness 2y agoLooks like Tamago targets multiple VM runtimes https://github.com/usbarmory/tamago?tab=readme-ov-file https://github.com/usbarmory/tamago?tab=readme-ov-file
- veggieroll 2y agoHow do you handle temp file space, timezone data, and other things that a minimal image provide?
- kfreds 2y agoTemp file space: Use RAM, or talk to host storage over Virtio. Timezone data etc: You would have to fetch that over the network, or from a metadata API such as the one Firecracker provides to VM guests.
- fpoling 2y agoServices rarely need timezone done. So if one is OK with supporting only UTC, Go runtime works fine without any timezene data. We use a minimal image to run in on AWS Nitro VM and it contains only kernel, init.d, the Go application file and TLS certificate roots with the root filesystem mounted over tmpfs. Note that Nitro VM uses a custom kernel provided by AWS so the new proposal is not relevant for us. But if we could run Go directly in that VM, it will surely makes things faster and saves like 10% memory overhead. And it will also avoid OOM killer and few other bad unwanted interactions between Go runtime and Linux kernel memory management.
- champtar 2y agoFor timezones data go already has https://pkg.go.dev/time/tzdata https://pkg.go.dev/time/tzdata
- advanderveer 2y agoI would be interested in this if it enabled deterministic simulation testing for the Go programming languages. There have been some efforts in this area but with little success.
- rcarmo 2y agoI use TinyGo, and it does that job well. Not sure if it’s necessary to mainline it.
- lcarsip 2y agoTinyGo targets an entirely different class of systems and is not something that can be upstream being a different compiler, see https://github.com/usbarmory/tamago/wiki/Frequently-Asked-Questions-(FAQ)#tinygo https://github.com/usbarmory/tamago/wiki/Frequently-Asked-Qu...