Michael Kelly, le sam. 14 nov. 2026 21:36:01 +0000, a ecrit: > On 14/11/2026 20:43, Samuel Thibault wrote: > > That would be a bit tricky because you'll have to remember how print and > > scroll interact etc. While, again, what would you want to actually > > memmove? The application output? It does not really make sense to scroll > > it since it's the gnumach output that needs to scroll, on top of the > > application output. > > I'm not concerned about the performance of these prints post-boot; it's the > affect on the boot time that concerns me. The boot output is much longer on > a real machine than a virtual one with lots more ACPI debug which should > perhaps be turned off ?
We could probably disable some ACPI prints yes, but better just fix the underlying issue :) > > As mentioned in a previous mail, it looks completely ok to me to > > implement scrolling by just drawing the known text of the gnumach > > console at the new position, and leave the rest alone. That'll be way > > faster than memmoving everything. > > All gnumach printfs during and after boot are alike. A print after boot must > still scroll the gnumach content the same as during boot. This would mean > that immediately after printing one line, sometime after boot when the Hurd > console is in use, that all the previous (numrows - 1) lines would suddenly > appear too. I don't think this is acceptable. I think it will be better than scrolling the application output. Samuel
