[HN Gopher] Why printk() is so complicated, and how to fix it (2... ___________________________________________________________________ Why printk() is so complicated, and how to fix it (2019) Author : Tomte Score : 30 points Date : 2021-04-05 06:54 UTC (1 days ago) (HTM) web link (lwn.net) (TXT) w3m dump (lwn.net) | [deleted] | amelius wrote: | Did anyone list all its requirements? | heinrichhartman wrote: | Slide 3? | https://www.linuxplumbersconf.org/event/4/contributions/290/... | igravious wrote: | https://news.ycombinator.com/item?id=21155348 | | Why printk() is so complicated, and how to fix it | (https://lwn.net/SubscriberLink/800946/a9ad9aba46f14e78/) | | 90 points |Tomte | 2 years ago | 13 comments | mauvehaus wrote: | Short version: because it needs work whether it's a sunny day or | the last embers of the burning world are cooling, and every | condition in between. It needs to allow formatting of an | arbitrary string, while not being able to allocate arbitrary | memory when called, or take any locks, for that matter. Oh, and | it needs to not slow the system to a crawl. And to be useful, its | output has to end up somewhere a person can see it. | | It would be a miracle if it _wasn 't_ incredibly complicated. ___________________________________________________________________ (page generated 2021-04-06 23:00 UTC)